Can not command line render anymore on 2 of 4 machines

[ivo_bakker]

When trying to render on our render farm 2 machines stopped working. We have 4 the same machines.
It seemed to have happend after a windows update. Before everything worked fine.

It's Maya 2023 with the Vray6. With Vray 5 it was the same problem.
So i am not sure it is a vray problem.

My log file says:

--------------------------------------

[MUSTER]Spawning process C:\Program Files\Autodesk\Maya2023\bin\Render.exe inside C:\Program Files\Autodesk\Maya2023\bin using the following command line flags:
[MUSTER]-r vray -threads 0 -proj "Z:\projecten\CBRE\Staverenstraat\Maya_Stavere nstr aat" -s 1.000 -e 1.000 -b 1.000 -x 5000 -y 3330 "Z:\projecten\CBRE\Staverenstraat\Maya_Stavere nstr aat\scenes\renders\Render_001.mb"
Starting "C:\Program Files\Autodesk\Maya2023\bin\mayabatch.exe"
[2022/Sep/19|15:13:54] V-Ray: V-Ray 6 for Maya version 6.00.02 from Aug 30 2022, 12:47:13
[2022/Sep/19|15:13:54] V-Ray: V-Ray core version is 6.00.09
Initializing V-Ray for Maya
[VMAYA PT] Loaded and initialized C:/Program Files/Chaos Group/V-Ray/Maya 2023 for x64/maya_vray/./translators/vraytr_bercon_special.dll
[VMAYA PT] Loaded and initialized C:/Program Files/Chaos Group/V-Ray/Maya 2023 for x64/maya_vray/./translators/vraytr_flakes2_translators.dll
[VMAYA PT] Loaded and initialized C:/Program Files/Chaos Group/V-Ray/Maya 2023 for x64/maya_vray/./translators/vraytr_geometry_translators.dll
[VMAYA PT] Loaded and initialized C:/Program Files/Chaos Group/V-Ray/Maya 2023 for x64/maya_vray/./translators/vraytr_texdirt_translator.dll
[VMAYA PT] Loaded and initialized C:/Program Files/Chaos Group/V-Ray/Maya 2023 for x64/maya_vray/./translators/vraytr_uvwgen_bercon.dll
[2022/Sep/19|15:13:56] V-Ray: Loading plugins from "C:/Program Files/Chaos Group/V-Ray/Maya 2023 for x64/maya_vray/vrayplugins\vray_*.dll"
[2022/Sep/19|15:13:56] V-Ray: 70 plugin(s) loaded successfully
[2022/Sep/19|15:13:56] V-Ray: Finished loading plugins.
Warning: V-Ray VolumeGrid: Loading shaders failed - no <*.txt> files in .
V-Ray VolumeGrid: loading C:/Program Files/Chaos Group/V-Ray/Maya 2023 for x64/maya_vray/./scripts/VRayVolumeGridInit.mel...
Warning: file: C:\Users\muster\Documents\maya\2023\prefs\filePath EditorRegistryPrefs.mel line 4: filePathEditor: Attribute 'aiImage.filename' is invalid or is not designated 'usedAsFilename'.
Warning: file: C:\Users\muster\Documents\maya\2023\prefs\filePath EditorRegistryPrefs.mel line 5: filePathEditor: Attribute 'aiPhotometricLight.aiFilename' is invalid or is not designated 'usedAsFilename'.
Warning: file: C:\Users\muster\Documents\maya\2023\prefs\filePath EditorRegistryPrefs.mel line 6: filePathEditor: Attribute 'aiStandIn.dso' is invalid or is not designated 'usedAsFilename'.
Warning: file: C:\Users\muster\Documents\maya\2023\prefs\filePath EditorRegistryPrefs.mel line 7: filePathEditor: Attribute 'aiVolume.filename' is invalid or is not designated 'usedAsFilename'.
V-Ray VolumeGrid: OK.
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node vrayMultiProjection (id: 1115335/0x001104C7)
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node VRayCurvature (id: 1115347/0x001104D3)
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node VRayPointParticleMtl (id: 1115353/0x001104D9)
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node VRayStochasticFlakesMtl (id: 1115359/0x001104DF)
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node VRayAlSurface (id: 1115350/0x001104D6)
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node VRayHairNextMtl (id: 1115320/0x001104B
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node VRayBerconNoise (id: 1115370/0x001104EA)
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node VRayFiltering (id: 1207503/0x00126CCF)
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node VRayCarPaint2Mtl (id: 1207504/0x00126CD0)
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node VRayFlakes2Mtl (id: 1207506/0x00126CD2)
[2022/Sep/19|15:13:57] V-Ray: Registered dynamic node VRayColorCorrection (id: 1207509/0x00126CD5)
info: MDL SDK 2019.1, build 317500.1752, 16 May 2019, nt-x86-64
info: Loaded library "C:\Program Files\Chaos Group\V-Ray\Maya 2023 for x64\maya_vray\bin\libvrayfreeimage.dll".
Initialized VP2.0 renderer {
Version : 2016.11.62.12. Feature Level 5.
Adapter :
Vendor ID: 0. Device ID :
Driver : OpenGL driver.
API : OpenGL V.4.6.
Max texture size : 16384 * 16384.
Max texture coords : 32
Shader versions supported (Vertex: 5, Geometry: 5, Pixel 5).
Shader compiler profile : (Best card profile)
Active stereo support available : 0
GPU Memory Limit : 11264 MB.
CPU Memory Limit : 124412 MB.
MultiDraw consolidation : enabled
}


OpenCL evaluator is attempting to initialize OpenCL.
// Maya exited with status 255
[MUSTER]Process terminated with exit code: 255

-----------------------------------

Does anyone know what could cause this ?
Tnx!

[ivo_bakker]

I found a fix to get it running again.
In the env file i disabled opencl. And now the machines can render again.
It does not solve the problem, but it is a fix.
And i do not know if it ever needs opencl during rendering ?

[Muhammed_Hamed]

Hey ivo_bakker

I'm not sure what OpenCL does here. I will ask around and get back to you

Best,
Muhammed

[yolov]

To answer the last question - V-Ray doesn't use OpenCL for rendering.
Looking at the log, everything went without issues until Maya exited, there's only a few Arnold warnings, which shouldn't be a problem at all.
It doesn't look related to V-Ray, at least by looking at the log.

What openCL did you disable to make it work and how exactly did you do it?

[ivo_bakker]

Thank you for sorting this out.

I disabled openCL in the env file in the windows user profile which is used by the render farm. I used this line: MAYA_DISABLE_OPENCL=1

[yolov]

Right-o, thanks.
There's a number of threads on the Autodesk forums that pop up in a google search for this.
I'm not 100% sure what OpenCL is used in Maya, but by the looks of it Maya uses OpenCL for its newer animation evaluation modes and probably other GPU-accelerated stuff too.
There were suggestions that an outdated video driver might be causing this, so updating the driver and re-enabling OpenCL might also do the trick.
Not sure if disabling OpenCL won't mess up something in the scene graph or animation evaluation.

That's pretty much what I could find so far.