Hello
We are using deadline 7.1.2.1
We are having a mix Linux/Windows farm
Everything works like a charm on windows but Linux slaves report their MAC ID as FF:FF:FF:FF:FF:FF
Any clue on what is wrong there ?
This is not so problematic as it is but the Wake On LAN depends on this to power on slaves so I need to fix this in the end
Thanks
Hey,
What you have shown here is a broadcast address which will send packets to all machines on the network. Where are you looking at this? Can you send a screenshot or the log you are looking at. To find a the mac address of a Linux machine you would use the command “ifconfig” the mac address will appear under HWaddr: mac-address.
Regards,
Charles
As you can see on screenshot it’s the deadline slave itself that is reporting wrong MAC ID,
Windows hosts on top are reporting correct information whereas Linux hosts are all erroneous
I guess this is related to the way the slave is launched and what it is authorized to do ?
OK we fixed that by using the MAC ID override property of slaves
Any way though to make the Linux slave automatically get the correct MAC ID ?
This strikes me as potentially bug-ish. The Slave should report the proper MAC address. You mentioned the Deadline version is 7.1.2.1. Which Linux distro and version are the Slaves using? Could you share the output of the following commands run on one of the Slaves in question?
cat /etc/*-releaseifconfigIf you are concerned about the sensitivity of any of this info, please put the info into a new Support Ticket, and we can follow up privately from there.
One thing I’ve noted is that guys in the Linux team seem not to have updated to the latest 7.1 release (7.1.1.4 instead of 7.1.2.1)
In any case that may be causing the issue I’m still waiting for some TDs to come back from vacation before pushing the 7.2 release
[code]jerome.du@rf030:~$ cat /etc/*-release
CentOS Linux release 7.0.1406 (Core)
NAME=“CentOS Linux”
VERSION=“7 (Core)”
ID=“centos”
ID_LIKE=“rhel fedora”
VERSION_ID=“7”
PRETTY_NAME=“CentOS Linux 7 (Core)”
ANSI_COLOR=“0;31”
CPE_NAME=“cpe:/o:centos:centos:7”
HOME_URL=“https://www.centos.org/”
BUG_REPORT_URL=“https://bugs.centos.org/”
CentOS Linux release 7.0.1406 (Core)
CentOS Linux release 7.0.1406 (Core)
[/code]
[code]jerome.du@rf030:~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx broadcast xxx.xxx.xxx.xxx
ether 00:30:48:f0:0b:72 txqueuelen 1000 (Ethernet)
RX packets 13710767 bytes 17539080410 (16.3 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3258763 bytes 1334128827 (1.2 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 28 memory 0xfbce0000-fbd00000
eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:30:48:f0:0b:73 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 29 memory 0xfbde0000-fbe00000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 0 (Local Loopback)
RX packets 269 bytes 17816 (17.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 269 bytes 17816 (17.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[/code]
Thanks Alcium,
Updating to the latest release version is always a good idea, so if you plan to do that anyway, we should wait and see whether that addresses the issue. The ifconfig results don’t show anything that should be tripping up Deadline, so either it’s a bug in Deadline, or there is an old or missing library somewhere somehow returning bad info. If you still have issues after the update, we can have our Support team test against your specific OS.