AWS Thinkbox Discussion Forums

[Linux[ Beta 6: Launcher service issues

I’ll start another thread in the beta discussion forum to cover some more general questions about the launcher service on Linux, but this definitely looks like a bug.

To reproduce (from a root shell), just run service deadlinelauncherservice start, then, service deadlinelauncherservice stop

I only caught this because I had a process monitor open and noticed that, rather than exiting, the “deadlinelaunche” [sic] process spiked to 100% CPU usage and hung instead. So I hunted down the log file and pulled this error off the tail end.

[code]
Could not find platform independent libraries
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to [:<exec_prefix>]
Deadline Launcher 6.0 [v6.0.0.49068 R]
Launcher Thread - Launcher thread initializing…
Launcher Thread - Remote administration is disabled
Launcher Thread - Launcher thread listening on port 5042
System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level
System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level
Full thread dump:

“Threapool monitor” tid=0x0x7ff977b8d700 this=0x0x7ff97d475138 thread handle 0x40c state : interrupted state owns ()

“” tid=0x0x7ff97ef7f760 this=0x0x7ff97d475ea0 thread handle 0x403 state : not waiting owns ()
at (wrapper managed-to-native) System.Threading.Thread.Sleep_internal (int) <0xffffffff>
at System.Threading.Thread.Sleep (int) <0x0001b>
at a.a (string[]) <0x00723>
at (wrapper runtime-invoke) .runtime_invoke_int_object (object,intptr,intptr,intptr) <0xffffffff>

“” tid=0x0x7ff977a41700 this=0x0x7ff97c497d68 thread handle 0x40d state : interrupted state owns ()

“Threadpool worker” tid=0x0x7ff9779bf700 this=0x0x7ff97c497af8 thread handle 0x40f state : interrupted state owns ()

“IO Threadpool worker” tid=0x0x7ff977a00700 this=0x0x7ff97c497c30 thread handle 0x40e state : interrupted state owns ()

“Timer-Scheduler” tid=0x0x7ff97c460700 this=0x0x7ff97d475000 thread handle 0x40a state : interrupted state owns ()
at (wrapper managed-to-native) System.Threading.WaitHandle.WaitOne_internal (System.Threading.WaitHandle,intptr,int,bool) <0xffffffff>
at System.Threading.WaitHandle.WaitOne (int,bool) <0x00087>
at System.Threading.WaitHandle.WaitOne (int) <0x0001a>
at System.Threading.Timer/Scheduler.SchedulerThread () <0x00b3e>
at System.Threading.Thread.StartUnsafe () <0x00071>
at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>[/code]

-Nathan

Hi Nathan,

I don’t think this error is specific to the launcher service, but this will be easier to determine in beta 7 since the launcher will no longer be redirecting its stdout to the deadlinelauncherservice log file.

I noticed this was a threading issue, and it turns out the launcher had the same threading issue the slave did when running in nogui mode. I’m guessing this could be related to this error, since it occurred while the launcher was running as a service (which uses the nogui flag).

The launcher threading issue will be fixed in beta 7 as well, so you’ll have to let us know if you continue to see this error after upgrading. We weren’t able to reproduce it here before or after fixing the launcher threading issue…

Cheers,

  • Ryan

Will do. Thanks Ryan.

Privacy | Site terms | Cookie preferences