[Linux] deadlinelauncher and zombie processes

[nrusch]

Beta 6 on Fedora 15

Two issues with the launcher:

First, the launcher process currently leaves zombies of every process it spawns hanging around indefinitely. It would be nice if these were properly cleaned up.

Second, running deadlinelauncher -shutdown from another shell doesn’t actually cause a running launcher process to exit. It echoes this to the terminal:

::ffff:100.100.200.32 has connected Launcher Thread - Received command: StopLauncher Shutting down Launcher Thread - Responded with: Success

…but the process never actually exits. If I then run something like deadlinelauncher -monitor from another shell, it spawns a new launcher process (alongside the one that never died), and this can continue ad infinitum.

-Nathan

[rrussell]

The zombie processes will be fixed in beta 7.

The issue with stopping the launcher is an interesting one. I wonder if maybe the original launcher didn’t shutdown all the way. That would explain why a new launcher was able to run, otherwise there would be a port conflict error.

We’ve logged this as a bug. We’ll see if we can reproduce and find a fix.

[nrusch]

Just to follow up, the zombie process issue also exists with the monitor for the deadlinecommand instances it spawns to connect to slave logs.

[rrussell]

Yup, we got that one too!