rendering problem with modo

Hello -
Brand new user of Deadline - just testing it out to use with modo. For now I have only installed the client on one machine in order to keep things simple while I learn the interface. As far as I can tell the monitor and client software are in okay, and I configured the plugin to point to the Modo 401 SP2 exe file, but when I submit a job (through modo via the script, or loading it manually in Monitor) the job starts, says it’s active, but nothing really happens.

The taskmanager shows modo.exe as active, but using very little CPU and RAM. The rendering does not proceed, but no error messages.

What am I doing wrong?

Thanks in advance,
Brett

Can you post the contents of the Slave application’s log window? Just select all the lines in the log window and copy and paste into your response. We’ll take a look to see if anything stands out.

Thanks!

  • Ryan

Thanks for the help.

The only log I can find is the error report (right-clicking on the slave node in Monitor) but it’s empty. I cannot find any other slave log options. There is no system tray icon or any other way I can find yet to access the slave - where would any other logs for the slave?

b

Did you install the client as a service? You can specify this in the Client installer. That’s the only reason I can think of for why you wouldn’t see the Slave Application when it is running. See here for an image of the slave (it’s the Mac version):
software.primefocusworld.com/sof … /slave.php

The log window shown here is where you can copy and paste the log out of. As an alternative, you can view the client log files by selecting Help -> Explore Log Folder in the Slave interface. Just find the slave log(s) and look for one that shows the slave starting the Modo job, then just idling.

One thing to check as well is that you’re pointing to the modo_cl.exe executable in the Modo plugin configuration, and not the modo.exe one.

Cheers,

  • Ryan

Thanks Ryan - I guess I did opt for the service route. I’m sure this is simple stuff for you guys but this is pretty steep setup for me :slight_smile:

I found the log and generated a new one by resubmitting the job - you can see in the text that it is looking for modo.exe but not sure if it’s going to the cl version. I have definitely tried it both ways in the plugin configuration and it says there that both are in the text string. Is it not updating somewhere else in the program that I need to do manually?

Log:

0: Task timeout is disabled.
0: Loaded job: Deadline_Test_oct10 (999_050_999_65e0f6dc)
0: INFO: StartJob: initializing script plugin Modo
0: INFO: About: Modo Plugin for Deadline
0: INFO: Starting monitored process: Modo0
0: INFO: Starting monitored managed process Modo0
0: INFO: Handling stdout that matches regex “Unknown command: .*”
0: INFO: Handling stdout that matches regex “.*failed with (-?[0-9]+)”
0: INFO: Stdout Handling Enabled: True
0: INFO: Popup Handling Enabled: True
0: INFO: Using Process Tree: True
0: INFO: Hiding DOS Window: True
0: INFO: Creating New Console: False
0: INFO: Render Executable: “C:\Program Files\Luxology\modo 401 sp2\modo.exe”
0: INFO: Render Argument: -cmd:"@“C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\plugins\render.pl” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt”" “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\BNR_Test_3.lxo”
0: INFO: Startup Directory: “C:\Program Files\Luxology\modo 401 sp2”
0: INFO: Process Priority: BelowNormal
0: INFO: Process is now running
0: INFO: Waiting until Modo is ready

The problem is likely that Deadline is using the modo.exe executable instead of modo_cl.exe. You mentioned that both were in the plugin configuration setting. Note that Deadline uses whichever executable it finds first in the list, so if modo.exe is defined first, that’s why Deadline is using it. Just remove the path to modo.exe and leave the one to modo_cl.exe and that should solve the problem.

Cheers,

  • Ryan

Okay - where can I find the actual list to edit it? I have tried pointing to the cl version using the configuration utility, and choosing to replace and not append the list, but I don’t think it worked. Can it be done manually?

b

  • it’s okay, I did it again with the plugin utility and I think it’s working. Thanks for the help!

b

First render went okay, and rendered exactly the same speed as modo so all appeared normal. I added a bit more complexity to the scene to test against a longer render time and now it’s stalling out again. I have tried submitting via modo/script and through monitor with the same result. Can you see what’s amiss from the log file below? Also: having a lot of trouble with the slave not allowing me to cancel the job. I suspend the job, and then cancel the active task on the slave, but often it doesn’t want to stop rendering so I have to choose to ‘stop slave’. Not sure if sometimes it just takes a lot longer to kill the job, or if there is a particular order/way to do it properly?

Thanks /b

2009-10-08 10:57:12: BEGIN - CHRONOS\SYSTEM
2009-10-08 10:57:12: Start-up
2009-10-08 10:57:12: 2009-10-08 10:57:12
2009-10-08 10:57:12: Deadline Slave 3.1 [v3.1.0.36430 R]
2009-10-08 10:57:13: slave initialization beginning.
2009-10-08 10:57:13: Repository time: 10/08/2009 10:57:13
2009-10-08 10:57:13: Info Thread - Created.
2009-10-08 10:57:15: The license file being used will expire in 34 days.
2009-10-08 10:57:19:
2009-10-08 10:57:19: Scheduler Thread - Plugin loaded in 0.03 seconds.
2009-10-08 10:57:20: Constructor: Modo
2009-10-08 10:57:20: fe80::75a3:71d9:544f:2687%10 has connected
2009-10-08 10:57:20: Listener Thread - Received message: OnLastTaskComplete CancelTask
2009-10-08 10:57:20: Listener Thread - Responded with: Success
2009-10-08 10:57:20: 0: Task timeout is disabled.
2009-10-08 10:57:20: 0: Loaded job: Untitled (999_050_999_17366ba5)
2009-10-08 10:57:20: 0: INFO: StartJob: initializing script plugin Modo
2009-10-08 10:57:21: 0: INFO: About: Modo Plugin for Deadline
2009-10-08 10:57:21: 0: INFO: Starting monitored process: Modo0
2009-10-08 10:57:21: 0: INFO: Starting monitored managed process Modo0
2009-10-08 10:57:22: 0: INFO: Handling stdout that matches regex “Unknown command: ."
2009-10-08 10:57:22: 0: INFO: Handling stdout that matches regex “.failed with (-?[0-9]+)"
2009-10-08 10:57:22: 0: INFO: Stdout Handling Enabled: True
2009-10-08 10:57:22: 0: INFO: Popup Handling Enabled: True
2009-10-08 10:57:22: 0: INFO: Using Process Tree: True
2009-10-08 10:57:22: 0: INFO: Hiding DOS Window: True
2009-10-08 10:57:22: 0: INFO: Creating New Console: False
2009-10-08 10:57:22: 0: INFO: Render Executable: “C:\Program Files\Luxology\modo 401 sp2\modo_cl.exe”
2009-10-08 10:57:22: 0: INFO: Render Argument: -cmd:"@“C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\plugins\render.pl” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt”" “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\BNR_Test_3.lxo”
2009-10-08 10:57:22: 0: INFO: Startup Directory: “C:\Program Files\Luxology\modo 401 sp2”
2009-10-08 10:57:22: 0: INFO: Process Priority: BelowNormal
2009-10-08 10:57:22: 0: INFO: Process is now running
2009-10-08 10:57:22: 0: INFO: Waiting until Modo is ready
2009-10-08 10:57:25: 0: STDOUT: Job filename: C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt
2009-10-08 10:57:25: 0: STDOUT: Ack filename: C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt
2009-10-08 10:57:25: 0: STDOUT: Sending ack: READY
2009-10-08 10:57:25: 0: STDOUT: Received command: QUERY: query platformservice path.path ? resource
2009-10-08 10:57:25: 0: STDOUT: Sending ack: C:\Program Files\Luxology\modo 401 sp2\resrc
2009-10-08 10:57:25: 0: INFO: LxResult config filename: C:\Program Files\Luxology\modo 401 sp2\resrc\msglxresult.cfg
2009-10-08 10:57:25: 0: Plugin rendering frame(s): 1
2009-10-08 10:57:25: 0: STDOUT: Received command: EXECUTE: select.itemType polyRender
2009-10-08 10:57:25: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 10:57:26: 0: STDOUT: Received command: EXECUTE: item.channel first 1
2009-10-08 10:57:26: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 10:57:26: 0: STDOUT: Received command: EXECUTE: item.channel last 1
2009-10-08 10:57:26: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 10:57:26: 0: STDOUT: Received command: EXECUTE: !render.animation {\Chronos\s\BNR_RENDERS\frames\deadline_test} EXR
2009-10-08 10:57:26: 0: STDOUT: @start modo_cl [32834] Luxology LLC
2009-10-08 10:57:26: 0: STDOUT: Rendering frame 1
2009-10-08 10:57:26: 0: STDOUT: Initializing render settings
2009-10-08 10:57:26: 0: STDOUT: Tableau initialized
2009-10-08 10:57:26: 0: STDOUT: Geometry cache initialized (11 surfaces)
2009-10-08 10:57:27: 0: STDOUT: Initialization complete
2009-10-08 10:57:27: 0: STDOUT: Frame Pass: Executing main render loop
2009-10-08 10:58:11: fe80::75a3:71d9:544f:2687%10 has connected
2009-10-08 10:58:11: Listener Thread - Received message: OnLastTaskComplete CancelTask
2009-10-08 10:58:11: Listener Thread - Responded with: Success
2009-10-08 10:58:47: Info Thread - Cancelling task because task filename “\chronos\s\DeadlineRepository\jobs\999_050_999_17366ba5\Rendering\999_050_999_17366ba5_00000_1-1.Chronos” could not be found, it was likely requeued
2009-10-08 10:58:47: sending cancel task command to plugin
2009-10-08 10:58:48: 0: In the process of canceling current task: ignoring exception thrown by PluginLoader
2009-10-08 10:58:52: Scheduler Thread - In the process of canceling current tasks: ignoring exception thrown by render thread 0
2009-10-08 10:58:53: Scheduler Thread - Canceling current task…
2009-10-08 10:59:05: fe80::75a3:71d9:544f:2687%10 has connected
2009-10-08 10:59:05: Listener Thread - Received message: OnLastTaskComplete CancelTask
2009-10-08 10:59:05: Listener Thread - Responded with: Success
2009-10-08 10:59:05: Scheduler Thread - Canceling current task…
2009-10-08 11:00:58:
2009-10-08 11:00:58: Scheduler Thread - Plugin loaded in 0.01 seconds.
2009-10-08 11:00:59: Constructor: Modo
2009-10-08 11:00:59: 0: Task timeout is disabled.
2009-10-08 11:00:59: 0: Loaded job: deadline_test2 (999_050_999_3ddbfa5e)
2009-10-08 11:00:59: 0: INFO: StartJob: initializing script plugin Modo
2009-10-08 11:00:59: 0: INFO: About: Modo Plugin for Deadline
2009-10-08 11:00:59: 0: INFO: Starting monitored process: Modo0
2009-10-08 11:00:59: 0: INFO: Starting monitored managed process Modo0
2009-10-08 11:00:59: 0: INFO: Handling stdout that matches regex "Unknown command: .

2009-10-08 11:00:59: 0: INFO: Handling stdout that matches regex “.failed with (-?[0-9]+)"
2009-10-08 11:00:59: 0: INFO: Stdout Handling Enabled: True
2009-10-08 11:00:59: 0: INFO: Popup Handling Enabled: True
2009-10-08 11:00:59: 0: INFO: Using Process Tree: True
2009-10-08 11:00:59: 0: INFO: Hiding DOS Window: True
2009-10-08 11:00:59: 0: INFO: Creating New Console: False
2009-10-08 11:00:59: 0: INFO: Render Executable: “C:\Program Files\Luxology\modo 401 sp2\modo_cl.exe”
2009-10-08 11:00:59: 0: INFO: Render Argument: -cmd:"@“C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\plugins\render.pl” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt”" “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\BNR_Test_3.lxo”
2009-10-08 11:00:59: 0: INFO: Startup Directory: “C:\Program Files\Luxology\modo 401 sp2”
2009-10-08 11:00:59: 0: INFO: Process Priority: BelowNormal
2009-10-08 11:00:59: 0: INFO: Process is now running
2009-10-08 11:00:59: 0: INFO: Waiting until Modo is ready
2009-10-08 11:01:02: 0: STDOUT: Job filename: C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt
2009-10-08 11:01:02: 0: STDOUT: Ack filename: C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt
2009-10-08 11:01:02: 0: STDOUT: Sending ack: READY
2009-10-08 11:01:03: 0: STDOUT: Received command: QUERY: query platformservice path.path ? resource
2009-10-08 11:01:03: 0: STDOUT: Sending ack: C:\Program Files\Luxology\modo 401 sp2\resrc
2009-10-08 11:01:03: 0: INFO: LxResult config filename: C:\Program Files\Luxology\modo 401 sp2\resrc\msglxresult.cfg
2009-10-08 11:01:03: 0: Plugin rendering frame(s): 1
2009-10-08 11:01:03: 0: STDOUT: Received command: EXECUTE: select.itemType polyRender
2009-10-08 11:01:03: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 11:01:03: 0: STDOUT: Received command: EXECUTE: item.channel first 1
2009-10-08 11:01:03: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 11:01:04: 0: STDOUT: Received command: EXECUTE: item.channel last 1
2009-10-08 11:01:04: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 11:01:04: 0: STDOUT: Received command: EXECUTE: !render.animation {\Chronos\s\BNR_RENDERS\frames\deadline_test2} EXR
2009-10-08 11:01:04: 0: STDOUT: @start modo_cl [32834] Luxology LLC
2009-10-08 11:01:04: 0: STDOUT: Rendering frame 1
2009-10-08 11:01:04: 0: STDOUT: Initializing render settings
2009-10-08 11:01:04: 0: STDOUT: Tableau initialized
2009-10-08 11:01:05: 0: STDOUT: Geometry cache initialized (11 surfaces)
2009-10-08 11:01:31: 0: STDOUT: Initialization complete
2009-10-08 11:01:31: 0: STDOUT: Frame Pass: Executing main render loop
2009-10-08 11:17:30: Repository time: 10/08/2009 11:17:30
2009-10-08 11:35:39: Info Thread - Cancelling task because task filename “\chronos\s\DeadlineRepository\jobs\999_050_999_3ddbfa5e\Rendering\999_050_999_3ddbfa5e_00000_1-1.Chronos” could not be found, it was likely requeued
2009-10-08 11:35:39: sending cancel task command to plugin
2009-10-08 11:35:40: 0: In the process of canceling current task: ignoring exception thrown by PluginLoader
2009-10-08 11:35:44: Scheduler Thread - In the process of canceling current tasks: ignoring exception thrown by render thread 0
2009-10-08 11:35:47: fe80::75a3:71d9:544f:2687%10 has connected
2009-10-08 11:35:48: Listener Thread - Received message: OnLastTaskComplete CancelTask
2009-10-08 11:35:48: Listener Thread - Responded with: Success
2009-10-08 11:35:48: Scheduler Thread - Canceling current task…
2009-10-08 11:36:08: Cleaning up orphaned tasks
2009-10-08 11:37:39: Repository time: 10/08/2009 11:37:39
2009-10-08 11:41:59: Purging obsolete pools and groups
2009-10-08 11:45:25: Purging temp directory
2009-10-08 11:45:25: Error purging file from temp directory: Access to the path ‘C:\Windows\TEMP\UDD1787.tmp’ is denied. (System.UnauthorizedAccessException)
2009-10-08 11:45:25: Error purging file from temp directory: Access to the path ‘C:\Windows\TEMP\UDD19AC.tmp’ is denied. (System.UnauthorizedAccessException)
2009-10-08 11:50:33: purging error reports older than 30 days
2009-10-08 11:55:21: Purging limit groups
2009-10-08 11:55:21:
2009-10-08 11:55:21: Scheduler Thread - Plugin loaded in 0.01 seconds.
2009-10-08 11:55:22: Constructor: Modo
2009-10-08 11:55:22: 0: Task timeout is disabled.
2009-10-08 11:55:22: 0: Loaded job: deadline_test4 (999_050_999_73780ce8)
2009-10-08 11:55:22: 0: INFO: StartJob: initializing script plugin Modo
2009-10-08 11:55:23: 0: INFO: About: Modo Plugin for Deadline
2009-10-08 11:55:23: 0: INFO: Starting monitored process: Modo0
2009-10-08 11:55:23: 0: INFO: Starting monitored managed process Modo0
2009-10-08 11:55:23: 0: INFO: Handling stdout that matches regex "Unknown command: .

2009-10-08 11:55:23: 0: INFO: Handling stdout that matches regex ".failed with (-?[0-9]+)"
2009-10-08 11:55:23: 0: INFO: Stdout Handling Enabled: True
2009-10-08 11:55:23: 0: INFO: Popup Handling Enabled: True
2009-10-08 11:55:23: 0: INFO: Using Process Tree: True
2009-10-08 11:55:23: 0: INFO: Hiding DOS Window: True
2009-10-08 11:55:23: 0: INFO: Creating New Console: False
2009-10-08 11:55:23: 0: INFO: Render Executable: “C:\Program Files\Luxology\modo 401 sp2\modo_cl.exe”
2009-10-08 11:55:23: 0: INFO: Render Argument: -cmd:"@“C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\plugins\render.pl” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt”" “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\BNR_Test_4.lxo”
2009-10-08 11:55:23: 0: INFO: Startup Directory: “C:\Program Files\Luxology\modo 401 sp2”
2009-10-08 11:55:23: 0: INFO: Process Priority: BelowNormal
2009-10-08 11:55:23: 0: INFO: Process is now running
2009-10-08 11:55:23: 0: INFO: Waiting until Modo is ready
2009-10-08 11:55:26: 0: STDOUT: Job filename: C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt
2009-10-08 11:55:26: 0: STDOUT: Ack filename: C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt
2009-10-08 11:55:26: 0: STDOUT: Sending ack: READY
2009-10-08 11:55:26: 0: STDOUT: Received command: QUERY: query platformservice path.path ? resource
2009-10-08 11:55:26: 0: STDOUT: Sending ack: C:\Program Files\Luxology\modo 401 sp2\resrc
2009-10-08 11:55:26: 0: INFO: LxResult config filename: C:\Program Files\Luxology\modo 401 sp2\resrc\msglxresult.cfg
2009-10-08 11:55:26: 0: Plugin rendering frame(s): 1
2009-10-08 11:55:26: 0: STDOUT: Received command: EXECUTE: select.itemType polyRender
2009-10-08 11:55:26: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 11:55:27: 0: STDOUT: Received command: EXECUTE: item.channel first 1
2009-10-08 11:55:27: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 11:55:27: 0: STDOUT: Received command: EXECUTE: item.channel last 1
2009-10-08 11:55:27: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 11:55:27: 0: STDOUT: Received command: EXECUTE: !render.animation {
}
2009-10-08 11:55:27: 0: STDOUT: @start modo_cl [32834] Luxology LLC
2009-10-08 11:55:27: 0: STDOUT: Rendering frame 1
2009-10-08 11:55:27: 0: STDOUT: Initializing render settings
2009-10-08 11:55:27: 0: STDOUT: Tableau initialized
2009-10-08 11:55:28: 0: STDOUT: Geometry cache initialized (11 surfaces)
2009-10-08 11:55:55: 0: STDOUT: Initialization complete
2009-10-08 11:55:55: 0: STDOUT: Frame Pass: Executing main render loop
2009-10-08 11:57:41: Repository time: 10/08/2009 11:57:41
2009-10-08 12:00:28: fe80::75a3:71d9:544f:2687%10 has connected
2009-10-08 12:00:29: Listener Thread - Received message: OnLastTaskComplete CancelTask
2009-10-08 12:00:29: Listener Thread - Responded with: Success
2009-10-08 12:00:38: Info Thread - Cancelling task because task filename “\chronos\s\DeadlineRepository\jobs\999_050_999_73780ce8\Rendering\999_050_999_73780ce8_00000_1-1.Chronos” could not be found, it was likely requeued
2009-10-08 12:00:38: sending cancel task command to plugin
2009-10-08 12:00:39: 0: In the process of canceling current task: ignoring exception thrown by PluginLoader
2009-10-08 12:00:43: Scheduler Thread - In the process of canceling current tasks: ignoring exception thrown by render thread 0
2009-10-08 12:00:43: Scheduler Thread - Canceling current task…
2009-10-08 12:01:28:
2009-10-08 12:01:28: Scheduler Thread - Plugin loaded in 0.01 seconds.
2009-10-08 12:01:29: Constructor: Modo
2009-10-08 12:01:29: 0: Task timeout is disabled.
2009-10-08 12:01:29: 0: Loaded job: deadline_test4 (999_050_999_73780ce8)
2009-10-08 12:01:29: 0: INFO: StartJob: initializing script plugin Modo
2009-10-08 12:01:29: 0: INFO: About: Modo Plugin for Deadline
2009-10-08 12:01:29: 0: INFO: Starting monitored process: Modo0
2009-10-08 12:01:30: 0: INFO: Starting monitored managed process Modo0
2009-10-08 12:01:30: 0: INFO: Handling stdout that matches regex "Unknown command: .

2009-10-08 12:01:30: 0: INFO: Handling stdout that matches regex ".failed with (-?[0-9]+)"
2009-10-08 12:01:30: 0: INFO: Stdout Handling Enabled: True
2009-10-08 12:01:30: 0: INFO: Popup Handling Enabled: True
2009-10-08 12:01:30: 0: INFO: Using Process Tree: True
2009-10-08 12:01:30: 0: INFO: Hiding DOS Window: True
2009-10-08 12:01:30: 0: INFO: Creating New Console: False
2009-10-08 12:01:30: 0: INFO: Render Executable: “C:\Program Files\Luxology\modo 401 sp2\modo_cl.exe”
2009-10-08 12:01:30: 0: INFO: Render Argument: -cmd:"@“C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\plugins\render.pl” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt”" “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\BNR_Test_4.lxo”
2009-10-08 12:01:30: 0: INFO: Startup Directory: “C:\Program Files\Luxology\modo 401 sp2”
2009-10-08 12:01:30: 0: INFO: Process Priority: BelowNormal
2009-10-08 12:01:30: 0: INFO: Process is now running
2009-10-08 12:01:30: 0: INFO: Waiting until Modo is ready
2009-10-08 12:01:33: 0: STDOUT: Job filename: C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt
2009-10-08 12:01:33: 0: STDOUT: Ack filename: C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt
2009-10-08 12:01:33: 0: STDOUT: Sending ack: READY
2009-10-08 12:01:33: 0: STDOUT: Received command: QUERY: query platformservice path.path ? resource
2009-10-08 12:01:33: 0: STDOUT: Sending ack: C:\Program Files\Luxology\modo 401 sp2\resrc
2009-10-08 12:01:33: 0: INFO: LxResult config filename: C:\Program Files\Luxology\modo 401 sp2\resrc\msglxresult.cfg
2009-10-08 12:01:33: 0: Plugin rendering frame(s): 1
2009-10-08 12:01:33: 0: STDOUT: Received command: EXECUTE: select.itemType polyRender
2009-10-08 12:01:33: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 12:01:34: 0: STDOUT: Received command: EXECUTE: item.channel first 1
2009-10-08 12:01:34: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 12:01:34: 0: STDOUT: Received command: EXECUTE: item.channel last 1
2009-10-08 12:01:34: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 12:01:34: 0: STDOUT: Received command: EXECUTE: !render.animation {
}
2009-10-08 12:01:34: 0: STDOUT: @start modo_cl [32834] Luxology LLC
2009-10-08 12:01:34: 0: STDOUT: Rendering frame 1
2009-10-08 12:01:34: 0: STDOUT: Initializing render settings
2009-10-08 12:01:34: 0: STDOUT: Tableau initialized
2009-10-08 12:01:35: 0: STDOUT: Geometry cache initialized (11 surfaces)
2009-10-08 12:02:01: 0: STDOUT: Initialization complete
2009-10-08 12:02:01: 0: STDOUT: Frame Pass: Executing main render loop
2009-10-08 12:15:46: fe80::75a3:71d9:544f:2687%10 has connected
2009-10-08 12:15:47: Listener Thread - Received message: OnLastTaskComplete CancelTask
2009-10-08 12:15:47: Listener Thread - Responded with: Success
2009-10-08 12:15:55: Info Thread - Cancelling task because task filename “\chronos\s\DeadlineRepository\jobs\999_050_999_73780ce8\Rendering\999_050_999_73780ce8_00000_1-1.Chronos” could not be found, it was likely requeued
2009-10-08 12:15:55: sending cancel task command to plugin
2009-10-08 12:15:56: 0: In the process of canceling current task: ignoring exception thrown by PluginLoader
2009-10-08 12:16:00: Scheduler Thread - In the process of canceling current tasks: ignoring exception thrown by render thread 0
2009-10-08 12:16:00: Scheduler Thread - Canceling current task…
2009-10-08 12:16:03:
2009-10-08 12:16:03: Scheduler Thread - Plugin loaded in 0.01 seconds.
2009-10-08 12:16:04: Constructor: Modo
2009-10-08 12:16:04: 0: Task timeout is disabled.
2009-10-08 12:16:04: 0: Loaded job: deadline_test4 (999_050_999_0aa702d5)
2009-10-08 12:16:04: 0: INFO: StartJob: initializing script plugin Modo
2009-10-08 12:16:04: 0: INFO: About: Modo Plugin for Deadline
2009-10-08 12:16:04: 0: INFO: Starting monitored process: Modo0
2009-10-08 12:16:04: 0: INFO: Starting monitored managed process Modo0
2009-10-08 12:16:04: 0: INFO: Handling stdout that matches regex “Unknown command: .*”
2009-10-08 12:16:04: 0: INFO: Handling stdout that matches regex ".failed with (-?[0-9]+)"
2009-10-08 12:16:04: 0: INFO: Stdout Handling Enabled: True
2009-10-08 12:16:04: 0: INFO: Popup Handling Enabled: True
2009-10-08 12:16:04: 0: INFO: Using Process Tree: True
2009-10-08 12:16:04: 0: INFO: Hiding DOS Window: True
2009-10-08 12:16:04: 0: INFO: Creating New Console: False
2009-10-08 12:16:04: 0: INFO: Render Executable: “C:\Program Files\Luxology\modo 401 sp2\modo_cl.exe”
2009-10-08 12:16:04: 0: INFO: Render Argument: -cmd:"@“C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\plugins\render.pl” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt” “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt”" “C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\BNR_Test_4.lxo”
2009-10-08 12:16:04: 0: INFO: Startup Directory: “C:\Program Files\Luxology\modo 401 sp2”
2009-10-08 12:16:04: 0: INFO: Process Priority: BelowNormal
2009-10-08 12:16:04: 0: INFO: Process is now running
2009-10-08 12:16:04: 0: INFO: Waiting until Modo is ready
2009-10-08 12:16:08: 0: STDOUT: Job filename: C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\job0.txt
2009-10-08 12:16:08: 0: STDOUT: Ack filename: C:\Windows\system32\config\systemprofile\AppData\Local\Frantic Films\Deadline\slave\jobsData\ack0.txt
2009-10-08 12:16:08: 0: STDOUT: Sending ack: READY
2009-10-08 12:16:08: 0: STDOUT: Received command: QUERY: query platformservice path.path ? resource
2009-10-08 12:16:08: 0: STDOUT: Sending ack: C:\Program Files\Luxology\modo 401 sp2\resrc
2009-10-08 12:16:08: 0: INFO: LxResult config filename: C:\Program Files\Luxology\modo 401 sp2\resrc\msglxresult.cfg
2009-10-08 12:16:08: 0: Plugin rendering frame(s): 1
2009-10-08 12:16:08: 0: STDOUT: Received command: EXECUTE: select.itemType polyRender
2009-10-08 12:16:08: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 12:16:08: 0: STDOUT: Received command: EXECUTE: item.channel first 1
2009-10-08 12:16:08: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 12:16:09: 0: STDOUT: Received command: EXECUTE: item.channel last 1
2009-10-08 12:16:09: 0: STDOUT: Sending ack: SUCCESS
2009-10-08 12:16:09: 0: STDOUT: Received command: EXECUTE: !render.animation {
}
2009-10-08 12:16:09: 0: STDOUT: @start modo_cl [32834] Luxology LLC
2009-10-08 12:16:09: 0: STDOUT: Rendering frame 1
2009-10-08 12:16:09: 0: STDOUT: Initializing render settings
2009-10-08 12:16:09: 0: STDOUT: Tableau initialized
2009-10-08 12:16:09: 0: STDOUT: Geometry cache initialized (11 surfaces)
2009-10-08 12:16:16: fe80::75a3:71d9:544f:2687%10 has connected
2009-10-08 12:16:17: Listener Thread - Received message: OnLastTaskComplete CancelTask
2009-10-08 12:16:17: Listener Thread - Responded with: Success
2009-10-08 12:16:36: 0: STDOUT: Initialization complete
2009-10-08 12:16:36: 0: STDOUT: Frame Pass: Executing main render loop
2009-10-08 12:16:39: fe80::75a3:71d9:544f:2687%10 has connected
2009-10-08 12:16:40: Listener Thread - Received message: StopSlave
2009-10-08 12:16:40: Listener Thread - Responded with: Success
2009-10-08 12:16:40: Info Thread - requesting slave info thread quit.
2009-10-08 12:16:40: sending cancel task command to plugin
2009-10-08 12:16:40: Info Thread - shutdown complete
2009-10-08 12:16:41: 0: In the process of canceling current task: ignoring exception thrown by PluginLoader
2009-10-08 12:16:44: Listener Thread - OnConnect: Listener Socket has been closed.
2009-10-08 12:16:46: Scheduler Thread - shutdown complete
2009-10-08 12:16:47: Checked license back in

Nothing looks out of the ordinary. When the job is “rendering”, what’s the CPU/memory usage like on the render node?

From looking at the log, it looks like the task is getting requeued and the slave is moving on. For example:

I should note that the slave might not instantly notice that the job has been canceled. The slave is only checking for this whenever it updates it’s status, which can be between every 20 and 40 seconds. Is this in line with the delay you’re seeing, or is it taking a lot longer?

Cheers,

  • Ryan

Thanks Ryan -
While rendering the CPU usage just fluctuates between 12% and 100%, pretty rhythmically, but nothing much happens. I let it run for 34 minutes with no result (the file renders directly in modo in 14 minutes). No indication of actual progress in the render (always showed 0% - but not sure if that is actually accurate anyway?)

I’m not sure what the job requeing means exactly, but I was cancelling the job first, and then if the slave did not seem to react I would cancel it there. The time lag was more like a minute or two. I was manually refreshing the slave to see it’s status but it still said ‘rendering’ until I killed the slave.

Job requeuing means that all the tasks that are currently rendering/completed re-enter the queue for processing (essentially, they enter the “Queued” state again). From looking at the log, everything appears to be functioning as normal. When you cancel the task that the slave is working on, it stops working on that task, but then moves on to the next available task (which could potentially be the same task). If you want a job to stop rendering, just suspend it from its right-click menu.

Unfortunately, Modo doesn’t print out any progress while it is rendering, so there is nothing to report back to the Monitor. The fact that it’s fluctuating between 12% and 100% indicates that it is doing something. The question is, what is it doing? :slight_smile:

Is it possible to upload a Modo scene that we can use here to try and reproduce the problem? Preferably one that doesn’t use any external references. If you can let us know the expected render time per frame as well, that would be great!

Also, just to confirm, are you rendering via Deadline on the same machine you’re testing the local render on? If you’re not, it might be worth trying to render on the render node via the Modo interface, just to make sure the scene renders properly on that machine when Deadline isn’t involved.

Cheers,

  • Ryan

Thanks for explaining that.

I can strip down the scene and send it to you. If you would be willing to look at the actual scene it might be better though, as this same file rendered okay the first time. In the problematic one when I turned on displacement and upped the anti-aliasing quality but essentially the rest is the same.

It’s all on one machine for now - just to keep things simple. So the deadline monitor and slave are both on the same machine, and it’s the one I am running modo on. The file renders fine directly out of modo, but I get the same problem with deadline from submitting via the modo script or by saving the file and submitting via Monitor.

Thanks /b

Sure, if you want to post the actual scene, that would be fine too.

Cheers,

  • Ryan

The stripped file seems to be having the same issue so hopefully you wont’ need it, but I can post it if you do. Here’s a link to the simple version.

simmsimaging.com/upload/file … le.lxo.zip

It’s rendering the same way via Deadline (CPU up and down and no joy) and in modo directly it is rendering fine and with steady full use of CPU’s.

Thanks for looking into it.
b

Just in case it helps: that modo scene rendered in 16 minutes on my i7 920 (so you have a sense of how long it should take).

b

Hmm, when Deadline is rendering the scene, are you still using the machine for anything else? The reason I ask is that Deadline starts up render processes with a below-normal priority. The reason for this is that it ensures the slave application can get some of the cpu when it needs to update its status (it’s a very minor operation, which doesn’t affect render times). Also, it helps when you need to remote into a machine that’s rendering. If the render process was running at normal priority, it’s likely that the remoting server process (ie: vnc) would struggle. However, as long as the machine isn’t used for anything else, 100% of the CPU will be devoted to Modo.

My machine is a Dual-Core AMD Opteron @ 2.6 GHz. I’m currently rendering through Modo without Deadline. I set the process priority to Modo to below-normal from the Task Manager so that I could continue working on my machine. It’s been rendering now for 30 minutes and it’s only 42% complete.

As a test, you could modify the Modo plugin for Deadline so that it starts the render process at normal priority. Open this file in a text editor:

\your\repository\plugins\Modo\Modo.py

Do a search for this line:

self.ProcessPriority = ProcessPriorityClass.BelowNormal

Change the code to this:

self.ProcessPriority = ProcessPriorityClass.Normal

Now save the file and submit a new job. Let us know if this helps to bring the render time through Deadline in line with that of Modo’s by itself.

Cheers,

  • Ryan

I will try it right now - thanks.

To answer your question though: I left the computer alone to let it run and see what would happen, and then during some of the tests I was messing around with other stuff - but it didn’t seem to matter either way.

b

That seems to have helped - it rendered via deadline in 16min, so just a bit longer than modo. I will run it again in both to verify, as I think even rendering in modo alone can have that kind of variation. However, the two successful renders I’ve done have both output .TGA files when I specified .EXR I am very sure about setting it in the submission dialog. Is there something else that needs to be done for that?

Thanks, b

So once I had the single slave version working I decided to try all 7 nodes. Getting the licensing working was a problem - for now I had to disable the firewall on the license server, the other steps in the manual didn’t seem to solve it. In any case, it’s functional for now :slight_smile:

However - still having the problem with the output saving as .TGA - and that messed up the tile rendering because it was looking for .exr files and could not find them. Also - some nodes appear to be doing the same thing - the CPU usage is up and down all over the place even though the process setting is on “normal” still. Rendering via modo’s built in DR maintains full CPU on all the nodes (at least rendering with brute force GI, which is what I’m doing for this test).

Is there another process priority setting that would apply to other slave nodes?

b