When starting Monitor I got a "Cannot assign requested address" Centos7

Deadline
1

Hi guys,
I got s sudden change of behavior on my Centos7 when starting my Deadline Monitor, telling me that he can’t assign the requested address, here is the return in my CLI:

Exception on Startup: Cannot assign requested address (System.Net.Sockets.SocketException)
at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at FranticX.Net.SocketUtils.CreateTcpListeningSocket(Int32 port, Boolean localOnly, Boolean forceIPv4)
at FranticX.Net.SocketUtils.CreateTcpListeningSocket(Int32 port, Boolean localOnly)
at Deadline.ListenerThread.a()
at Deadline.ListenerThread.Initialize()
at Deadline.Monitor.MonitorManager.StartThreads()
at DeadlineMonitor.DeadlineMonitorApp.Main(String[] args)

Deadline Monitor will now exit.

Any idea ?

Thank you,

Tanguy

3

Hello!

What version of Deadline is running on this machine? Was Deadline running on this machine correctly previously and there have been no recent updates?

The app is trying to bind to an ip and port. Either the port or the ip we are trying to start the application on is not available.

The app should be selecting a random port every time you launch it and should be written to

/var/lib/Thinkbox/Deadline10/monitor.ini

If it was a port issue I would expect an Address Already In Use error.

I suspect its an issue with the machine finding a network address to bind to. If you run ifconfig in Terminal do you have multiple NICs? Do any of them display a network address?

4

Hi,
I am currently running 10.1.0.12 on one of my ws and 10.1.0.10 on the Repo / Db
Both run on CentOS 7.7.
Another ws works without any issue and runs as well a 7.7 BUT it is / was a direct install and not an update from 7.4 to 7.7.
I have the 2 ETH from the HP Z and I have a 10Gbe card which is the one connected with a Jumbo frame enabled 9000. Both ws runes en 10 Gbe cards as well as the QNAP, on 10Gbe too.
I got it working actually but for some reason my ws stop running the Deadline, Moniot or Worker.
I probably had some updates when I was trying to licensed my Redshift ONLY on this machine. Which I did not succeeded for lack of support for CentOS 7 from Redshift on the redshiftLicenseingTool. So I deifintely ended up trying to isntall a libQtGUI and libQt4.so.4 desperately without success, maybe that kinda crap some of my setup.

here is my ifconfig print:
[tang@bod-WS ~]$ ifconfig
eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 18:60:24:87:ba:97 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 20 memory 0xd3e00000-d3e20000

enp7s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 18:60:24:87:ba:98 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 memory 0xd3700000-d377ffff

ens6f0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether a0:36:9f:20:7d:54 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

ens6f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255
ether a0:36:9f:20:7d:56 txqueuelen 1000 (Ethernet)
RX packets 1621210 bytes 1717108445 (1.5 GiB)
RX errors 0 dropped 13043 overruns 0 frame 0
TX packets 1565200 bytes 992987824 (946.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 29011 bytes 21613594 (20.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29011 bytes 21613594 (20.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.33.1.18 netmask 255.255.255.255 destination 10.33.1.17
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 796640 bytes 795871115 (759.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 919067 bytes 784193325 (747.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:50:96:7b 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

I run expressvpn as well, maybe that is an issue but I run that guy on all my machine actually BUT the licnese server / Repo / DB

Thank you for helping !
Tanguy

5

Well looks like the MTU got changed to 1500, probably me trying to debug…

6

So actually I got it to work, by killing my expressvpn.
Anyway I can workaround that constraint ?

Thank you for any tips or cool tricks to make it happen !

Tanguy

7

Its sounds like an network interface priority issue where the Deadline apps are trying to startup up on tun0. You will want to try to set ens6f1 to be a higher priority.

$ sudo vi /etc/sysconfig/network-scripts/ifcfg-tun0
METRIC=20

$ sudo vi /etc/sysconfig/network-scripts/ifcfg-ens6f1
METRIC=10

sudo service network restart
8

Heads up, looks like this is a problem with IPv6 being disabled and .net core which is being used in 10.1.

There’s a fix in 10.1 SP2, so keep an eye out for that version.

1 Like