Hey everyone,
This has been a longstanding issue for us since DL4. Whenever we delete more than ~50 jobs, the jobs are successfully removed, but DL locks up directly after, and crashes. This only seems to occur while in Super User Mode.
DL version 5.0.0.44500
OS X version 10.6.7
Any help would be greatly appreciated! Thanks in advance,
Dylan
Hi Dylan,
We can’t seem to reproduce this behavior here. I tried deleting 50, 100, and 200 jobs at a time (both in super user and normal mode), and the Monitor didn’t crash.
Can you reproduce this problem every time, or is it more of a random problem? The next time this happens, can you find the Monitor log from the session where it crashed and post it? You can find the log folder from the Monitor by selecting Help -> Explore Log Folder.
Finally, which version of Mono do you have installed?
Cheers,
Hi Ryan,
Seems to be more of a random problem now – I just deleted 72 jobs and it worked fine. The next time it happens, I’ll post the logs here. We’re running Mono 2.6.7_3.
Thanks!
-Dylan
Hi All,
Attached is an example of the crash that occurs. This happens nearly every time we attempt to delete any number of jobs. Let me know if you figure anything out!
Thanks,
Dylan
Hey Dylan,
Thanks for the movie, but a log would be really helpful too.
We just need the Monitor log from the session where it crashed. You can find the log folder from the Monitor by selecting Help -> Explore Log Folder. If you’re not sure which Monitor log to grab, just grab all of them.
Also, it could help if you launched the Monitor from a terminal, and then when it crashes, just copy & paste the contents of the terminal into a text file and post it. Sometimes the low level stuff doesn’t make it into the Deadline logs.
Thanks!
Hey Ryan,
No problem, attached is the log.
Thanks,
Dylan
deadlinemonitor(Royale-pro-07)-2011-07-13-0000.log (5 KB)
Thanks! I can see from the log how it just dies while removing jobs, and unfortunately the crash message doesn’t make it into the log. If you could launch the Monitor from a terminal, and then grab the output after the crash, I’m sure it will contain better info.
Thanks!