Hi Ryan
I got a weird error
0: INFO: Process exit code: 137
basically , the job is a Mayabatch running a system call (to a python program)
sometimes it works at first attempt , sometimes 4 times to succeed. (even on the same machine)
So i suspect either a timeout somewhere , or maybe the system call doesnt work sometimes (the farm is centos5)
Is this code error from Deadline , or Maya, or Centos ?
Your help is appreciated .
Guy
Hey Guy,
I did some googling, and exit code 137 indicates that the process was killed. It could have been killed by an external process, or could have sent the kill command to itself. I don’t think it’s something specific to Maya or Deadline.
Have you tried running executing the python script outside the context of Maya? If crashes a few times after repeated attempts, then at least you know it’s something specific to what the script is doing.
Cheers,
Hi Ryan
After a couple hours of investigation and tracing-debugging , i finally found out the truth and you were close…
2 years ago , we set up a mecanism to avoid 2 maya batch running at same time on the same slave , thus if deadline was not aware that a previous Maya was not closed correctly , the script would kill it .
In my case my maya command was launching a python script , this script also creating a new mayabatch… so 2 at the same time. So the old one was killed and code error 137 return to deadline
Temporarely, we commented out the script to let 2 maya running at the same time, but this is not a final solution.
So Maybe there a possiblity to instruct Deadline to check (via a pre job script) if a previous maya is running , instead of letting the OS do the check.
Any idea in deadline ?
Cheers
Guy
Hey Guy,
There used to be a bug in Deadline that could prevent it from closing the mayabatch process for a job, but this was fixed back in 4.1. So if you guys are using this version or later, you probably don’t need to worry about this.
Regardless, you could probably create a PreLoad.py script for the MayaBatch plugin to do this check:
thinkboxsoftware.com/deadlin … -_Optional
The PreLoad.py script is run at the start of every new job for the plugin it was created for. The script could check for a running instance, and then call FailRender( “blah blah” ) to fail the render if another instance is detected.
Cheers,