Slaves dont pick up the render job in submited DBR job


#1

Hi guys,
very new to Deadline.
Everythign setup properly but i cant seem to get the slaves to join the submited DBR job.
i got rid of all the spawners in the backgroud.
i can successfully render locally through the interactive DBR.
But whenever i send the job with DBR checked and distributed render (in vray) checked, only the master renders :-/
Any idea whats wrong?
I am running out of clues.

I can easily render with DR on though backburner.
Woudl be happy and thankful for some ideas and help!

Cheers!
M


#2

on the slaves it behaves very weirdly, the spawners startup and die while the job is running.
i can see in the system tray spawners appearing and disappearing and sometimes i can even see as much as 3 spawners at the same time.


#3

i have whitelisted only 1 node, the rest is on the blacklist and i got this error:

Error: RenderTask: Unexpected exception (03.01.2019 12:21:07; Error rendering frame 0: An unexpected exception has occurred in the network renderer and it is terminating.)

v Deadline.Plugins.PluginWrapper.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

=======================================================

Type

=======================================================

RenderPluginException


2019-01-03 12:20:35: 0: INFO: Executing global asset transfer preload script ‘C:\Users\pixelbox12\AppData\Local\Thinkbox\Deadline10\slave\RENDERMAN4\plugins\5c2deff8bdcac7640852fa6c\GlobalAssetTransferPreLoad.py’

2019-01-03 12:20:35: 0: INFO: Looking for AWS Portal File Transfer…

2019-01-03 12:20:35: 0: INFO: Looking for File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py…

2019-01-03 12:20:35: 0: INFO: Could not find AWS Portal File Transfer.

2019-01-03 12:20:35: 0: INFO: AWS Portal File Transfer is not installed on the system.

2019-01-03 12:20:35: 0: INFO: Start Job called - starting up 3dsCmd plugin

2019-01-03 12:20:35: 0: INFO: V-Ray DBR: Delaying load of 3dsmaxcmd until RenderTasks phase

2019-01-03 12:20:35: 0: Done executing plugin command of type ‘Start Job’

2019-01-03 12:20:35: 0: Plugin rendering frame(s): 0

2019-01-03 12:20:36: 0: Executing plugin command of type ‘Render Task’

2019-01-03 12:20:36: 0: INFO: Render Tasks called

2019-01-03 12:20:36: 0: INFO: Releasing DBR job as MASTER has now been elected: RENDERMAN4

2019-01-03 12:20:36: 0: INFO: Rendering with 3ds Max Cmd Version: 2019

2019-01-03 12:20:36: 0: INFO: Not enforcing a build of 3ds Max because version 2014 and later is 64 bit only

2019-01-03 12:20:36: 0: INFO: Slave 3ds Max Cmd Version: 21.3.0.3250

2019-01-03 12:20:36: 0: INFO: Slave 3ds Max Version: 21.3.0.3250

2019-01-03 12:20:36: 0: INFO: Submitted from 3ds Max Version: 21.3.0.3250

2019-01-03 12:20:36: 0: INFO: Secure mode enabled: False

2019-01-03 12:20:36: 0: INFO: Creating output directories if necessary…

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Configuring Distributed Render Job…

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Dynamic Start: True

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Plugin Config Settings to be applied to local file: vray_dr.cfg

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Port Range: 20204

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Use Local Machine: True

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Transfer Missing Assets: False

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Use Cached Assets: False

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Cache Limit Type: None

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Cache Limit: 100

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Starting distributed render immediately

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Use IP Address instead of Hostname: False

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: 0 machines available currently to DBR, local machine will be used unless configured in plugin settings to be ignored

2019-01-03 12:20:36: 0: INFO: Language code string: ENU

2019-01-03 12:20:36: 0: INFO: Language sub directory: en-US

2019-01-03 12:20:36: 0: INFO: 3dsmax user profile path: C:\Users\pixelbox12\AppData\Local\Autodesk\3dsMax\2019 - 64bit\ENU

2019-01-03 12:20:36: 0: INFO: 3dsmax plugcfg directory: C:\Users\pixelbox12\AppData\Local\Autodesk\3dsMax\2019 - 64bit\ENU\en-US\plugcfg

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Backing up original config file to: C:\Users\pixelbox12\AppData\Local\Thinkbox\Deadline10\slave\renderman4\jobsData\5c2deff8bdcac7640852fa6c\vray_dr.cfg

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Deleting original config file: C:\Users\pixelbox12\AppData\Local\Autodesk\3dsMax\2019 - 64bit\ENU\en-US\plugcfg\vray_dr.cfg

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Config file created: C:\Users\pixelbox12\AppData\Local\Autodesk\3dsMax\2019 - 64bit\ENU\en-US\plugcfg\vray_dr.cfg

2019-01-03 12:20:36: 0: INFO: V-Ray DBR: Waiting 10 seconds to give V-Ray Spawner time to initialize on other machines

2019-01-03 12:20:46: 0: INFO: V-Ray DBR: Ready to go, moving on to distributed render

2019-01-03 12:20:46: 0: INFO: V-Ray DBR: Rendering frame 0

2019-01-03 12:20:46: 0: INFO: Scene file to render: "C:\Users\pixelbox12\AppData\Local\Thinkbox\Deadline10\slave\RENDERMAN4\jobsData\5c2deff8bdcac7640852fa6c\debug.max"

2019-01-03 12:20:46: 0: INFO: Starting monitored managed process CmdProcess

2019-01-03 12:20:46: 0: INFO: Stdout Redirection Enabled: True

2019-01-03 12:20:46: 0: INFO: Stdout Handling Enabled: True

2019-01-03 12:20:46: 0: INFO: Popup Handling Enabled: True

2019-01-03 12:20:46: 0: INFO: QT Popup Handling Enabled: True

2019-01-03 12:20:46: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: True

2019-01-03 12:20:46: 0: INFO: Using Process Tree: True

2019-01-03 12:20:46: 0: INFO: Hiding DOS Window: True

2019-01-03 12:20:46: 0: INFO: Creating New Console: False

2019-01-03 12:20:46: 0: INFO: Running as user: pixelbox12

2019-01-03 12:20:46: 0: INFO: Executable: "C:\Program Files\Autodesk\3ds Max 2019\3dsmaxcmd.exe"

2019-01-03 12:20:46: 0: INFO: Argument: "C:\Users\pixelbox12\AppData\Local\Thinkbox\Deadline10\slave\RENDERMAN4\jobsData\5c2deff8bdcac7640852fa6c\debug.max" -v:4 -start:0 -end:0 -cam:"PhysCamera001" -w:5000 -h:3750 -pixelAspect:1.0 -atmospherics:true -renderHidden:false -effects:true -useAreaLights:false -displacements:true -force2Sided:false -videoColorCheck:false -superBlack:false -renderFields:false -fieldOrder:Odd -skipRenderedFrames:false -renderElements:true -useAdvLight:true -computeAdvLight:false -gammaCorrection:false -continueOnError -rfw:0 -videopostJob:0

2019-01-03 12:20:46: 0: INFO: Full Command: "C:\Program Files\Autodesk\3ds Max 2019\3dsmaxcmd.exe" "C:\Users\pixelbox12\AppData\Local\Thinkbox\Deadline10\slave\RENDERMAN4\jobsData\5c2deff8bdcac7640852fa6c\debug.max" -v:4 -start:0 -end:0 -cam:"PhysCamera001" -w:5000 -h:3750 -pixelAspect:1.0 -atmospherics:true -renderHidden:false -effects:true -useAreaLights:false -displacements:true -force2Sided:false -videoColorCheck:false -superBlack:false -renderFields:false -fieldOrder:Odd -skipRenderedFrames:false -renderElements:true -useAdvLight:true -computeAdvLight:false -gammaCorrection:false -continueOnError -rfw:0 -videopostJob:0

2019-01-03 12:20:46: 0: INFO: Startup Directory: "C:\Program Files\Autodesk\3ds Max 2019"

2019-01-03 12:20:46: 0: INFO: Process Priority: BelowNormal

2019-01-03 12:20:46: 0: INFO: Process Affinity: default

2019-01-03 12:20:46: 0: INFO: Process is now running

2019-01-03 12:20:46: 0: STDOUT: 03.01.2019 12:20:46; 1 frames


#4

so to sum up my findings today:

Checking Vray DBR Off load to enable the job to be rendered with various render slaves completely kills the files submission. Job doesnt get picked up. Spawners start and crash and i get errors.

Sending the job without the DBR works and vacant node picks it up and renders using the local threads.

Is there a problem with MAX 2019.3? Or Vray NEXT Update 1.1?

Where is the support here? Can i please get some answers?

Thank you!
Martin


#5

Hey Martin,

I did a test with V-Ray DBR, Max 2019.3, and V-Ray Next and was able to successfully render. I did this using the Submit V-Ray DBR to Deadline submitter.

“C:\DeadlineRepository10\submission\3dsmaxVRayDBR\Installers\3dsmaxVRayDBR-submitter-windows-installer.exe”

This test was successful. It looks like you are submitting a V-Ray DBR Offload job via the SMTD. That will be my next test. But in the meantime as a workaround you try to use the V-Ray DBR Submitter to see if that works for you.


#6

Off-load worked for me as well, what Deadline 10 version are you on? Can you please give the V-Ray DBR submitter a try? I’d like to see if that gives us some more details into what the problem might be.

Thanks!

Charles


#7

i ve successfully tried this as well.
If i understand it well this is for rendering on the local workstation while using reserved slaves nodes in a local DR session.
This works from beginning.
Slave nodes are picked up from everyhere where the DEADLINE CLIENT is running.

BUT

offloading doesnt work and behaves like i described above. It almost looks like the spawners that the clietns run cant find licenses and get killed??

Using the latest downloadable version of Deadline.

I am using the evaluation period at the moment. I ve bought 10 licenses from Swedish reseller but they returned the money and said they cant resell to Czech Republic :-/ There is no reseller in Czech. So after we figure out the problems with the DR offloading i will have to tackle this problem. Evaluation ends by 6th of FEB.

I am also getting the IvP6 errors when i send animation jobs but it renders.


#8

i really need the offload to get working as i need to work on the local workstation


#9

do i need to do somethign with the “Render threads per task = 0” value in the JOB tab of the SMTD dialogue window?


#10

Hey Martin,

Sorry for the delay here. I’m going to see if we can’t extend your trial period while we figure this one out.

For your error here, it seems like it’s a problem between Max and V-Ray as the error is happening when we run this command: (it’s a long one)

"C:\Program Files\Autodesk\3ds Max 2019\3dsmaxcmd.exe" "C:\Users\pixelbox12\AppData\Local\Thinkbox\Deadline10\slave\RENDERMAN4\jobsData\5c2deff8bdcac7640852fa6c\debug.max" -v:4 -start:0 -end:0 -cam:"PhysCamera001" -w:5000 -h:3750 -pixelAspect:1.0 -atmospherics:true -renderHidden:false -effects:true -useAreaLights:false -displacements:true -force2Sided:false -videoColorCheck:false -superBlack:false -renderFields:false -fieldOrder:Odd -skipRenderedFrames:false -renderElements:true -useAdvLight:true -computeAdvLight:false -gammaCorrection:false -continueOnError -rfw:0 -videopostJob:0

I don’t believe we send the “debug.max” file. Can you try running the above command (you’ll have to change that path) and see if it also complains with “An unexpected exception has occurred in the network renderer and it is terminating”?

Thanks,

Edwin


#11

Hello, i am curretly talking to Chaos guys, will let you know how this progresses!