Setting up deadline. Working with Modo. 2 separate errors.

Deadline
1

So I’m very excited to get Deadline up and running in our shop. Having a few issues getting started. Would really appreciate any help.

I’m testing out the system with 3 computers (obviously, only using 2 at any time with the license free mode).

To summarize. I’m all mac, mainly using Lightwave and Modo. Right now we’re just trying to get Modo implemented.

Computer 1 (Mac Pro 12 core) seems to be working just fine; loads, renders, great.
Computer 2 (Mac Pro 8 core) will get a job, open modo for rendering, scene starts to load, then Modo immediately crashes. Deadline then reopens modo and goes through the process all over again.

Computer 3 (Mac Pro 8 core), I can’t get deadline applications to install. The installer gets most of the way through, writes out the app files and directories to the applications folder, then I get a message that there was an error installing, contact the software vendor. I believe this issue has something to do with mono.

So, first off, I’d like to first try to nail down the issue with Computer2 which has deadline running okay, but continuously crashes Modo on startup.

I get this in the console. It’s gibberish to me, can anyone tell what might be going on?

Process: modo [9419]
Path: /Applications/modo.app/Contents/MacOS/modo
Identifier: com.luxology.modo
Version: 501(41483) (501)
Code Type: X86-64 (Native)
Parent Process: mono [8595]

EDIT: TRIMMED FOR EASIER READING

2

Hi there,

When modo crashes on the 2nd machine, is there an error report generated for the job that it was rendering? If so, can you post one of the error reports? It would be interesting to see what Deadline was telling modo to do when it crashed.

Thanks!

  • Ryan
3

Hi Ryan.

Here’s what the apple error report says. Let me know if it’s what you’re looking for.

Process: modo [4538]
Path: /Applications/modo.app/Contents/MacOS/modo
Identifier: com.luxology.modo
Version: 501(41483) (501)
Code Type: X86-64 (Native)
Parent Process: mono [4377]

EDIT: TRIMMED FOR EASIER READING

4

I don’t think that is what Ryan was looking for. There are log files generated by Deadline during its operation. You can review these from the monitor application to see what might be going wrong and it’s those that are potentially more useful to see what Deadline was trying to do.

5

Is this more like it? I found this in the error reports of the deadline repository.

<?xml version="1.0" encoding="us-ascii"?> 2011-05-10T02:11:39.436114-07:00 Oddball-octoball 0 Exception during render: An error occurred in RenderTasks(): Monitored managed process "Modo0" has exited or been terminated. at Deadline.Plugins.ScriptPlugin.RenderTasks (Int32 startFrame, Int32 endFrame, System.String& outMessage) [0x00000] in <filename unknown>:0 <_SlaveVersionString>v4.1.0.43205 R Untitled wesball Oddball-octoball 2011-05-10T02:11:04 Modo 1-1 33 RenderPluginException at Deadline.Plugins.Plugin.RenderTask (Int32 startFrame, Int32 endFrame) [0x00000] in <filename unknown>:0 at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask () [0x00000] in <filename unknown>:0 /Contents/MacOS/modo" 0: INFO: Render Argument: -cmd:"@\"/Users/wesball/Deadline/slave/plugins/render.pl\" \"/Users/wesball/Deadline/slave/jobsData/job0.txt\" \"/Users/wesball/Deadline/slave/jobsData/ack0.txt\"" "/Volumes/ODDBALL/PROJECTS/RUIN-Playground/RUIN-Dunes/3D/SandDunesDeadlineTest.lxo" 0: INFO: Startup Directory: "/Applications/modo.app/Contents/MacOS" 0: INFO: Process Priority: BelowNormal 0: INFO: Process is now running 0: INFO: Waiting until Modo is ready 0: STDOUT: 2011-05-10 02:11:15.558 modo[57411:903] *** __NSAutoreleaseNoPool(): Object 0x104101080 of class NSCFLocale autoreleased with no pool in place - just leaking 0: STDOUT: 2011-05-10 02:11:15.560 modo[57411:903] *** __NSAutoreleaseNoPool(): Object 0x115f65930 of class NSCFData autoreleased with no pool in place - just leaking 0: STDOUT: Job filename: /Users/wesball/Deadline/slave/jobsData/job0.txt 0: STDOUT: Ack filename: /Users/wesball/Deadline/slave/jobsData/ack0.txt 0: STDOUT: Sending ack: READY 0: STDOUT: Received command: QUERY: query platformservice path.path ? resource 0: STDOUT: Sending ack: /Applications/modo.app/Contents/Resources 0: INFO: LxResult config filename: /Applications/modo.app/Contents/Resources/msglxresult.cfg 0: Plugin rendering frame(s): 1 0: STDOUT: Received command: EXECUTE: select.itemType polyRender 0: STDOUT: Sending ack: SUCCESS 0: STDOUT: Received command: EXECUTE: item.channel first 1 0: STDOUT: Sending ack: SUCCESS 0: STDOUT: Received command: EXECUTE: item.channel last 1 0: STDOUT: Sending ack: SUCCESS 0: STDOUT: Received command: EXECUTE: !render.animation {*} 0: WARNING: Monitored managed process Modo0 is no longer running Scheduler Thread - Render Thread 0 threw an error: Scheduler Thread - Exception during render: An error occurred in RenderTasks(): Monitored managed process "Modo0" has exited or been terminated. at Deadline.Plugins.ScriptPlugin.RenderTasks (Int32 startFrame, Int32 endFrame, System.String& outMessage) [0x00000] in <filename unknown>:0 2380267520 28 2145805927 25 14 55296 9
6

Thanks! That’s what I was looking for. Based on this output…

…modo is crashing when is told to render the frame. Out of curiosity, are you able to launch modo on this machine and render the same scene locally without Deadline? Just trying to figure out if the problem is with the way Deadline is controlling modo, of if it’s a more general modo problem.

Cheers,

  • Ryan
7

Yes. I can render fine without deadline.

8

Okay, the next thing to do is to try and mimic what Deadline is doing. On the problematic machine, open modo and load the scene you’re trying to render. Then select System -> Evaluate, and run this command:

select.itemType polyRender

Repeat this process for the following three commands:

item.channel first 1
item.channel last 1
!render.animation {*}

If that works, that means that Deadline must be doing something else that modo isn’t happy with.

Thanks!

  • Ryan
9

Hey Ryan. Ran these commands. All seems good. Modo renders fine.

What should I try next?

10

Thanks for trying that out. I think at this point it might be best to wait until Deadline 5 is released, which should be either tomorrow or Friday. We’ve made some significant improvements to our modo support, including better logging, and running modo in nogui mode on OSX. Maybe running modo in nogui mode might help, and if not, hopefully the modo render log will provide some insight.

If you want access to Deadline 5 right now, just let me know and I’ll give you beta access.

Thanks for your patience! :slight_smile:

  • Ryan

PS: I trimmed the posts with the console crash dumps. Makes it easier to follow this thread. :slight_smile:

11

Cool Ryan. I will test out the Deadline 5 when you get it out. I may ask for beta if it’s not out by the weekend.

So just an update. I’ve now tried to get Deadline running on all 5 machines in the office. I get the same crash. So strange since the one computer works fine. The only difference I can think of is this 12 core is the newest machine… while all the other computers are a few years old. Not sure if that would have anything to do with it.

I have one more newer machine I could try, but that’s the one I mentioned previously that won’t even let meinstall the Deadline clients. I believe it has something to do with the mono framework, as I when the installer crashes, it logs a mono crash report.

Here’s the screengrab of the error message during the install. Along with the log text. Any thoughts? Thanks again for the help.

http://dl.dropbox.com/u/4354451/Fail.png

Process: mono [17617]
Path: /Library/Frameworks/Mono.framework/Versions/2.6.7/bin/mono
Identifier: mono
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: sh [17610]

Date/Time: 2011-05-12 15:46:35.138 -0700
OS Version: Mac OS X 10.6.7 (10J869)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000a110000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Application Specific Information:
abort() called

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x97b6f156 __kill + 10
1 libSystem.B.dylib 0x97b6f148 kill$UNIX2003 + 32
2 libSystem.B.dylib 0x97c01899 raise + 26
3 libSystem.B.dylib 0x97c179b8 abort + 93
4 DeadlineCommand 0x000c24f4 mono_handle_native_sigsegv + 980
5 DeadlineCommand 0x00010e76 mono_sigsegv_signal_handler + 306
6 libSystem.B.dylib 0x97b7445b _sigtramp + 43
7 ??? 0xffffffff 0 + 4294967295
8 libfontconfig.1.dylib 0x02f741ee FcLangSetHasLang + 506
9 libfontconfig.1.dylib 0x02f75d89 FcCompareLang + 149
10 libfontconfig.1.dylib 0x02f75910 FcCompareValueList + 448
11 libfontconfig.1.dylib 0x02f75b79 FcCompare + 180
12 libfontconfig.1.dylib 0x02f7678c FcFontSetMatch + 355
13 libfontconfig.1.dylib 0x02f7698f FcFontMatch + 85
14 libgdiplus.dylib 0x03d8e65c GdipCreateFontFamilyFromName + 780
15 ??? 0x04e65f12 0 + 82206482
16 ??? 0x04e65ea5 0 + 82206373
17 ??? 0x04e65e4e 0 + 82206286
18 ??? 0x04e65e0f 0 + 82206223
19 ??? 0x04e65c05 0 + 82205701
20 ??? 0x04e65bab 0 + 82205611
21 ??? 0x04e65b4d 0 + 82205517
22 ??? 0x04e65aea 0 + 82205418
23 ??? 0x04e65a7d 0 + 82205309
24 ??? 0x04e658fb 0 + 82204923
25 ??? 0x04e657e9 0 + 82204649
26 ??? 0x04e657a8 0 + 82204584
27 ??? 0x0070023b 0 + 7340603
28 DeadlineCommand 0x00010c41 mono_jit_runtime_invoke + 1372
29 DeadlineCommand 0x001d0c7a mono_runtime_invoke + 138
30 DeadlineCommand 0x001cb964 mono_runtime_class_init_full + 1783
31 DeadlineCommand 0x0000fe5f mono_jit_compile_method_inner + 3418
32 DeadlineCommand 0x00010086 mono_jit_compile_method_with_opt + 497
33 DeadlineCommand 0x00010220 mono_jit_compile_method + 50
34 DeadlineCommand 0x001cc39f mono_compile_method + 73
35 DeadlineCommand 0x000c3914 mono_magic_trampoline + 2514
36 ??? 0x0055d066 0 + 5623910
37 ??? 0x04e64a2c 0 + 82201132
38 ??? 0x04e656b4 0 + 82204340
39 ??? 0x04e6562c 0 + 82204204
40 ??? 0x0070023b 0 + 7340603
41 DeadlineCommand 0x00010c41 mono_jit_runtime_invoke + 1372
42 DeadlineCommand 0x001d0c7a mono_runtime_invoke + 138
43 DeadlineCommand 0x001cb964 mono_runtime_class_init_full + 1783
44 DeadlineCommand 0x0000fe5f mono_jit_compile_method_inner + 3418
45 DeadlineCommand 0x00010086 mono_jit_compile_method_with_opt + 497
46 DeadlineCommand 0x00010220 mono_jit_compile_method + 50
47 DeadlineCommand 0x001cc39f mono_compile_method + 73
48 DeadlineCommand 0x000c3914 mono_magic_trampoline + 2514
49 ??? 0x0055d066 0 + 5623910
50 ??? 0x04e6452b 0 + 82199851
51 ??? 0x04e64454 0 + 82199636
52 ??? 0x04e64021 0 + 82198561
53 ??? 0x04e60f93 0 + 82186131
54 ??? 0x04e60e9b 0 + 82185883
55 ??? 0x04e60e71 0 + 82185841
56 ??? 0x04e60e3c 0 + 82185788
57 ??? 0x00700309 0 + 7340809
58 ??? 0x00700704 0 + 7341828
59 DeadlineCommand 0x00010c41 mono_jit_runtime_invoke + 1372
60 DeadlineCommand 0x001d0c7a mono_runtime_invoke + 138
61 DeadlineCommand 0x001d278d mono_runtime_exec_main + 622
62 DeadlineCommand 0x001d2127 mono_runtime_run_main + 808
63 DeadlineCommand 0x0009810d mono_jit_exec + 200
64 DeadlineCommand 0x00098347 main_thread_handler + 558
65 DeadlineCommand 0x0009a2aa mono_main + 6666
66 DeadlineCommand 0x00005ca3 main + 49
67 DeadlineCommand 0x00005c46 start + 54

Thread 1:
0 libSystem.B.dylib 0x97b0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x97b0e807 mach_msg + 68
2 DeadlineCommand 0x00125a37 mach_exception_thread + 82
3 libSystem.B.dylib 0x97b3b7fd _pthread_start + 345
4 libSystem.B.dylib 0x97b3b682 thread_start + 34

Thread 2: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x97b34922 kevent + 10
1 libSystem.B.dylib 0x97b3503c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x97b344f9 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x97b3429e _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x97b33d21 _pthread_wqthread + 390
5 libSystem.B.dylib 0x97b33b66 start_wqthread + 30

Thread 3:
0 libSystem.B.dylib 0x97b339b2 __workq_kernreturn + 10
1 libSystem.B.dylib 0x97b33f48 _pthread_wqthread + 941
2 libSystem.B.dylib 0x97b33b66 start_wqthread + 30

Thread 4:
0 libSystem.B.dylib 0x97b3c046 __semwait_signal + 10
1 libSystem.B.dylib 0x97b67ec5 nanosleep$UNIX2003 + 188
2 DeadlineCommand 0x0022e01b collection_thread + 48
3 libSystem.B.dylib 0x97b3b7fd _pthread_start + 345
4 libSystem.B.dylib 0x97b3b682 thread_start + 34

Thread 5:
0 libSystem.B.dylib 0x97b3c046 __semwait_signal + 10
1 libSystem.B.dylib 0x97b3bd02 _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x97b3d998 pthread_cond_wait$UNIX2003 + 73
3 DeadlineCommand 0x00233a56 _wapi_handle_timedwait_signal_handle + 586
4 DeadlineCommand 0x0023380a _wapi_handle_wait_signal_handle + 40
5 DeadlineCommand 0x00249f6c WaitForSingleObjectEx + 631
6 DeadlineCommand 0x002595d0 mono_sem_timedwait + 34
7 DeadlineCommand 0x002595ac mono_sem_wait + 32
8 DeadlineCommand 0x0016322d finalizer_thread + 107
9 DeadlineCommand 0x002096a2 start_wrapper + 592
10 DeadlineCommand 0x0024c13d thread_start_routine + 202
11 DeadlineCommand 0x00270da4 GC_start_routine + 107
12 libSystem.B.dylib 0x97b3b7fd _pthread_start + 345
13 libSystem.B.dylib 0x97b3b682 thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x97c17967 ecx: 0xbfffd1ec edx: 0x97b6f156
edi: 0x0110f63a esi: 0x02f7a87e ebp: 0xbfffd208 esp: 0xbfffd1ec
ss: 0x00000023 efl: 0x00000286 eip: 0x97b6f156 cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0xa0953000

12

We’re holding off Deadline 5 until Monday, so I’ve sent you a private message with the beta info.

When you installed the Deadline Client, did you leave the “Use X11 Driver” option enabled? If not, try reinstalling the Client with that option enabled (we’re actually enforcing this in v5 because it’s much more stable in X11 mode).

If you are using the X11 drivers, maybe try uninstalling and reinstalling Mono on this machine. Also, double check that you installed the Intel version and not the PPC one. The uninstall script can be found here:
mono-project.com/Mono:OSX#Un … n_Mac_OS_X

Deadline 5 is compatible with Mono 2.10.x, so you could try installing that version too if you move to Deadline 5 this weekend.

Cheers,

  • Ryan