Hey there,
we’ve just set up everything in deadline a couple of days ago and it seems to work pretty well so far. There’s just one weird problem I can’t find the reason for. As soon as we shutdown and restart / reboot one of our renderclients which runs deadline as daemon it starts the slave with the name “localhost” and the machine name “localhost.localdomain” instead of it’s real names.
sh /opt/Thinkbox/Deadline7/bin/deadlinelauncherservice stop
sh /opt/Thinkbox/Deadline7/bin/deadlinelauncherservice start
The rendernodes are all CentOS 6.4
fixes it, but it’s a pain to manually restart the service after each boot. Anyone any idea what might cause this?
Hello Nyk,
So when the slave starts up, it asks the machine/OS what the hostname of the machine is, and then reports that as it’s hostname to the DB. I am unsure why it would be seeing itself as localhost, but that is not something we can control. Can you verify how the machines are provisioned? I am wondering if we need to try to find a way to slow the load of the launcher service in your case until the machine sees it’s correct hostname.
Hi,
By chance, another client reported this issue on our beta forum last week and it was fixed earlier today! The fix will ship with v7.1 beta 5. Essentially, we cache various bits of Slave information. However, the machine name can change whilst the application is running if DNS is not available at the exact moment, that the Deadline Slave starts up and so the incorrect cache persists. We have now changed the way the cache now works. Unfortunately, I can’t think of an immediate work-around. Are you interested in joining the beta? If so, please email “beta [at] thinkboxsoftware [dot] com” for the NDA to sign for access.
Indeed it was the slave starting too early in the process. We’ve tried to delay the startup but it wouldn’t start late enough without adding a pretty bad workout like “sleep x” in the startup script. So for now we’ve just hardcoded the hostname so it’s the right one even before the dns delivers it.
Looking forward to 7.1 stable in this case. I’ll try reverting the changes as soon as it’s out.
Thank you!
