Using v6 beta9 on linux. On some hosts, the launcher will run without errors but won’t start a slave instance no matter what I do. The launcher log has no errors in it. When I start the launcher the log shows:
2013-01-21 11:23:22: BEGIN - r033\root
2013-01-21 11:23:22: Deadline Launcher 6.0 [v6.0.0.49761 R]
2013-01-21 11:23:22: slave config names: 1
2013-01-21 11:23:22: Local version file: /opt/Thinkbox/Deadline6/bin/Version
2013-01-21 11:23:22: Network version file: /mnt/Z/apps/DeadlineRepository6/bin/Linux/Version
2013-01-21 11:23:22: Comparing version files…
2013-01-21 11:23:22: Version files match
2013-01-21 11:23:22: Launching Slave:
2013-01-21 11:23:22: Launcher Thread - Launcher thread initializing…
2013-01-21 11:23:22: Remote Administration is now enabled
2013-01-21 11:23:22: Launcher Thread - Remote administration is enabled
2013-01-21 11:23:22: Launcher Thread - Launcher thread listening on port 17060
But the slave is not running and status is stalled. If using remote control I do a slave restart then this is what I see in the logs:
2013-01-21 11:24:36: ::ffff:10.101.2.159 has connected
2013-01-21 11:24:36: Launcher Thread - Received command: ForceRelaunchSlave r033
2013-01-21 11:24:36: No slave to shutdown
2013-01-21 11:24:36: Launcher Thread - Responded with: Success|
2013-01-21 11:24:46: Local version file: /opt/Thinkbox/Deadline6/bin/Version
2013-01-21 11:24:46: Network version file: /mnt/Z/apps/DeadlineRepository6/bin/Linux/Version
2013-01-21 11:24:46: Comparing version files…
2013-01-21 11:24:46: Version files match
2013-01-21 11:24:46: Launching Slave: r033
but the slave does not start. There are a handful of hosts like this. There are no slave logs in /var/log/Thinkbox/Deadline6
Thanks,
Nick