Hi,
We have Deadline 6.1 Running - and the thing is that not all slaves seem to connect to pulse
Pulse itself runs on a Windows Server 2012 Maschine - so there shouldn’t be any limitation in the TCP/IP Stack like in non-Server Windows.
See the attached Screenshot, from 32 online slaves only half are connected to Pulse
How to fix this?
i can provide additional Info if needed
Hello,
So there could be a number of possible issues at play here. What would be really helpful would be a slave log from one of the slaves that cannot connect, and some background info. Is it always these same machines? Are there times or instances when the number that could not connect went up or down dramatically? Are there any patterns you have discerned among the machines involved? Thanks.
Hi,
solved!
While the Logs didn’t contain anything intereseting, I’ve changed the pulse auto configuration to the Hostname instead of the IP-Address - now all slaves connect!
Which brings me to the next Question: why does Deadline Use IPv6 Adresses?
In Deadline 7.0 and up, we no longer use ipv6 by default, instead we use the one with the default gateway, which is usually ipv4. I think this may come, in part from the technology for IPv6 not being mature enough when the original code came in, and when we realized the issues the implementation caused, fixed it pretty quickly.
