Deadline wont start

Deprecated Deadline 10 Discussion
1

Hi,
I have set-up my own Deadline image with 10.0.0.30.
Launcher and Slave wont start .
Launcher Log :
[root@ip-10-34-0-28 Deadline10]# cat /var/log/Thinkbox/Deadline10/deadlinelauncher-ip-10-34-0-28-2017-08-24-0001.log
2017-08-24 14:20:38: BEGIN - ip-10-34-0-28\root
2017-08-24 14:20:38: Operating System: Linux
2017-08-24 14:20:38: CPU Architecture: x86_64
2017-08-24 14:20:38: CPUs: 1
2017-08-24 14:20:38: Video Card: Cirrus Logic GD 5446
2017-08-24 14:20:38: Deadline Launcher 10.0 [v10.0.0.30 Release (a8fddef27)]
2017-08-24 14:20:38: Launcher Thread - Launcher thread initializing…
2017-08-24 14:20:38: creating listening socket on port: 39201
2017-08-24 14:20:38: writing listening socket to launcher file: 39201
2017-08-24 14:20:38: Launcher Thread - Launcher thread listening on port 17000
2017-08-24 14:20:38: Launcher is running as a service or daemon, delaying startup for 60 seconds
2017-08-24 14:20:38: This delay can be adjusted by setting the LauncherServiceStartupDelay setting in the system deadline.ini file
2017-08-24 14:21:13: Warning: Unable to obtain a lock for the synchronization of the Python API files. This is likely due to another Deadline process performing the synchronization and can be ignored if this warning occurs only once.
2017-08-24 14:21:13: If this warning persists after restarting Deadline, please contact Thinkbox Support.
2017-08-24 14:21:13: Auto Configuration: Picking configuration based on: ip-10-34-0-28 / 10.34.0.28
2017-08-24 14:21:13: Auto Configuration: Match found for rule mangesh (IPMatch)
2017-08-24 14:21:13: Auto Configuration: Match found for rule (IPMatch)
2017-08-24 14:21:13: Auto Configuration: A ruleset has been found
2017-08-24 14:21:13: Auto Configuration: Region value is empty, ignoring…

Slave Log :
[root@ip-10-34-0-28 Deadline10]# cat /var/log/Thinkbox/Deadline10/deadlineslave-ip-10-34-0-28-2017-08-24-0001.log
2017-08-24 13:57:58: BEGIN - ip-10-34-0-28\root
2017-08-24 13:57:58: Operating System: Linux
2017-08-24 13:57:58: CPU Architecture: x86_64
2017-08-24 13:57:58: CPUs: 1
2017-08-24 13:57:58: Video Card: Cirrus Logic GD 5446
2017-08-24 13:57:58: Deadline Slave 10.0 [v10.0.0.30 Release (a8fddef27)]
2017-08-24 13:57:58: Scanning for auto configuration
2017-08-24 13:58:02: Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration
2017-08-24 13:58:02: Connecting to repository
2017-08-24 13:58:25: Info Thread - Created.

Need help to setup this.
Thanks
Mangesh

2

Hey Mangesh,

Looks like both the Launcher and the Slave processes are starting, are they not appearing in the Monitor?

How are you connecting them to your repository? Direct connection or through the Deadline Proxy Server?

Thanks,
Eric

3

Hi Eric,
Thanks for the quick reply.
Yes they are not appearing in the Monitor.
Repository connection is Direct.

Thanks

5

Hi Osiowi,
Thanks will do this upgrade and keep you posted.

Thanks

6

Hi Osiowi,

After upgrading to 10.0.0.41 all the slaves are running and appearing in my Deadline monitor.

Thanks

7

Great! Glad I could help.