Deadline 9.0.3 Slave won't launch

[Nick_Weeden]

Hi,

We’ve just auto-upgraded to 9.0.3 and now multiple render machines won’t launch their slave. If I manually navigate to the folder and launch the .exe I can at least get it to write out a log file:

2017-06-20 13:18:15: BEGIN - RENDER-07-164\render
2017-06-20 13:18:15: Operating System: Windows 7 Professional (SP1)
2017-06-20 13:18:15: CPU Architecture: x64
2017-06-20 13:18:15: CPUs: 40
2017-06-20 13:18:15: Video Card: ASPEED Graphics Family(WDDM)
2017-06-20 13:18:15: Deadline Slave 9.0 [v9.0.3.0 Release (c5f056bb6)]
2017-06-20 13:18:15: Another Slave named ‘RENDER-07-164’ is already running. Use the ‘-name’ setting to launch a slave with an alternative name. Slave will now shutdown.
2017-06-20 13:18:15: Slave - Final cleanup
2017-06-20 13:18:15: Slave - Shutdown complete

There are no other slaves running on the system, I restarted, uninstalled and re-installed Deadline and still couldn’t get it to launch. I then found a blank named “.ini” file in “C:\ProgramData\Thinkbox\Deadline9\slaves” which I deleted and now the slave will launches. We’ve had this happen on multiple machines and periodically we get situations where the slave won’t launch. Just wanted to check if this was something breaking during the update. As it’s incredibly frustrating to debug!

Thanks

Nick

[eamsler]

No, it’s been around a long while actually. It’s down to how the Launcher talks to the Slave, and the fact that the Slave assumes another instance is already running if the TCP port it used on last launch is in use (even if the app in question is not the Slave).

I’m pretty sure we’re working on that now.

[Nick_Weeden]

Hi Edwin,

Thanks for the update. I’ll keep an eye on it to see if it does it again, it doesn’t happen very often but I’m pretty sure something similar has caught me out on previous updates.

Thanks

Nick