Hi there,
It seems that there is still an issue that sometimes the deadline launcher / monitor just does not launch / restart. Seems to be connected to previously open sessions from that monitor, but i’m not sure.
Here is an email i received last night around 1.30am:
Yeah, I’m seeing this too. It seems like when this happens, if I shutdown all instances of the Deadline applications, then they can all start up normally again. It seems to be that they’re listening socket doesn’t get closed for some reason, so they think another instance is already running.
We need to do some digging on why this happens, or maybe change up our code that tests to see if another instance is already running.
Yeah definitely seems like i have to shut down anything deadline related, then i can restart properly
Looks like we’ve figured this one out. It was related to another issue I think you guys ran into where an old mayabatch process was still running and you couldn’t start the slave until you killed the mayabatch process. We just needed to set a flag to prevent the child process from inheriting any handles from the parent process.
The fix will be included in beta 10.
Cheers,
Glorious thanks!