Vray Proxy Error

[Dman3d]

Nothing so far has worked as far as reinstalling things etc.
IT found a big issue with our server switches and some issue with server drive, not clear what.
New switches to be ordered.

[Dman3d]

However there is also the issue with Anima on the farm, render node version is installed
tons of these types of errors

2024-11-01 12:34:29: 0: STDOUT: WARNING: material StreamMaterial_5 has no supportable Techniques and will be blank. Explanation:
2024-11-01 12:34:29: 0: STDOUT: Pass 0: vertex program PBR_VP cannot be used - not supported.
2024-11-01 12:34:29: 0: STDOUT: Pass 0: vertex program PBR_MRT_VP cannot be used - not supported.

[Joelaff]

Doesn't sound like a switch issue to me, as that would manifest itself in all sorts of places, not just when rendering. But I hope you get it sorted.

I know the NAS oplock thing drove me nuts for about a week until I finally figured that out, and there is very little info out there regarding it. But who knows.

Please do keep us updated. I always like to hear what the problem was so we can avoid it.

[Dman3d]

Got more verbose error logging for one of the errors:

2024-11-01 14:28:12: 0: INFO: Building light cache... [00:00:37.5] [596:31:23.8 est]

2024-11-01 14:28:12: 0: STDOUT: Premature end of JPEG file

2024-11-01 14:28:12: 0: STDOUT: Premature end of JPEG file

2024-11-01 14:28:12: 0: STDOUT: Premature end of JPEG file

2024-11-01 14:28:12: 0: STDOUT: 00:27:08 4269MB WARNING | signal caught: error C0000006

2024-11-01 14:28:12: 0: STDOUT: ****

2024-11-01 14:28:12: 0: STDOUT: * Arnold 7.2.4.1 [1fee86c4] windows x86_64 clang-15.0.7 oiio-2.4.1 osl-1.12.9 vdb-7.1.1 adlsdk-7.4.2.47 clmhub-3.1.1.43 rlm-14.2.5 optix-6.6.0 2023/10/17 03:22:02

2024-11-01 14:28:12: 0: STDOUT: * CRASHED in memmove

2024-11-01 14:28:12: 0: STDOUT: * signal caught: error C0000006

2024-11-01 14:28:12: 0: STDOUT: *

2024-11-01 14:28:12: 0: STDOUT: * backtrace:

2024-11-01 14:28:12: 0: STDOUT: >> 0 0x00007fffda871242 [VCRUNTIME140] memmove

2024-11-01 14:28:12: 0: STDOUT: * 1 0x00007fff4fd4cdfe [vray ] PluginManagerUtilsBase::writeDotDependencyGraph

2024-11-01 14:28:12: 0: STDOUT: * 2 0x00007fff4fd40157 [vray ] PluginManagerUtilsBase::writeDotDependencyGraph

2024-11-01 14:28:12: 0: STDOUT: * 3 0x00007fff4e7ecb4c [vray ] VUtils::VRayPluginHost::getAPIMajorVersion

2024-11-01 14:28:12: 0: STDOUT: * 4 0x00007fff4e7f3607 [vray ] VUtils::VRayPluginHost::getAPIMajorVersion

2024-11-01 14:28:12: 0: STDOUT: * 5 0x00007fff4e7d3193 [vray ] VUtils::VRayPluginHost::getAPIMajorVersion

2024-11-01 14:28:12: 0: STDOUT: * 6 0x00007fff4e72c9f2 [vray ] VUtils::VRayPluginHost::getAPIMajorVersion

2024-11-01 14:28:12: 0: STDOUT: * 7 0x00007fff4e72cde1 [vray ] VUtils::VRayPluginHost::getAPIMajorVersion

2024-11-01 14:28:12: 0: STDOUT: * 8 0x00007fff5e604c41 [vrender2024 ] isVRayBitmapUsedAsNormalMap

2024-11-01 14:28:12: 0: STDOUT: * 9 0x00007fff5e5fde63 [vrender2024 ] clearTextureCache

2024-11-01 14:28:12: 0: STDOUT: * 10 0x00007fff5e5f4930 [vrender2024 ] MaxSDK::MeshChannelContainer::~MeshChannelContaine r

2024-11-01 14:28:12: 0: STDOUT: * 11 0x00007fff1dd52ac1 [ ]

2024-11-01 14:28:12: 0: STDOUT: * 12 0x00007fff5e7ba917 [vrender2024 ] VUtils::VRenderMtl::shade

2024-11-01 14:28:12: 0: STDOUT: * 13 0x00007fff5e75362f [vrender2024 ] isMaxMaterialSwitcher

2024-11-01 14:28:12: 0: STDOUT: * 14 0x00007fff5e7b4c05 [vrender2024 ] VUtils::VRenderInstance::fullShade

2024-11-01 14:28:12: 0: STDOUT: * 15 0x00007fff4e409678 [vray ] VUtils::IntersectionData::setSurfaceProperties

2024-11-01 14:28:12: 0: STDOUT: * 16 0x00007fff4e40a1ee [vray ] VUtils::VRayCore::shadeRayResult

2024-11-01 14:28:12: 0: STDOUT: * 17 0x00007fff4e408c1d [vray ] VUtils::VRayCore::getTimeInFrames

2024-11-01 14:28:12: 0: STDOUT: * 18 0x00007fff4e90f00c [vray ] PluginManagerUtilsBase::writeDotDependencyGraph

2024-11-01 14:28:12: 0: STDOUT: * 19 0x00007fff4e40b676 [vray ] VUtils::VRayCore::traceRay

2024-11-01 14:28:12: 0: STDOUT: * 20 0x00007fff4e4021b0 [vray ] VUtils::VRayCameraSampler::traceCamera

2024-11-01 14:28:12: 0: STDOUT: * 21 0x00007fff4e45ba26 [vray ] VUtils::VRayRenderer::traceScreenRay

2024-11-01 14:28:12: 0: STDOUT: * 22 0x00007fff4e3bac20 [vray ] AssetHashManager::setHash

2024-11-01 14:28:12: 0: STDOUT: * 23 0x00007fff5ea625bb [vrender2024 ] VRayListerElement::getWidget

2024-11-01 14:28:12: 0: STDOUT: * 24 0x00007ffff14f514b [ucrtbase ] o__beginthread

2024-11-01 14:28:12: 0: STDOUT: * 25 0x00007ffff3ab7374 [KERNEL32 ] BaseThreadInitThunk

2024-11-01 14:28:12: 0: STDOUT: * 26 0x00007ffff3e7cc91 [ntdll ] RtlUserThreadStart

2024-11-01 14:28:12: 0: STDOUT: *

2024-11-01 14:28:12: 0: STDOUT: * loaded modules:

2024-11-01 14:28:12: 0: STDOUT: * 0x00007fffda860000 VCRUNTIME140

2024-11-01 14:28:12: 0: STDOUT: * 0x00007fff4e2d0000 vray

2024-11-01 14:28:12: 0: STDOUT: * 0x00007fff5e500000 vrender2024

2024-11-01 14:28:12: 0: STDOUT: * 0x00007ffff14d0000 ucrtbase

2024-11-01 14:28:12: 0: STDOUT: * 0x00007ffff3aa0000 KERNEL32

2024-11-01 14:28:12: 0: STDOUT: * 0x00007ffff3e30000 ntdll

2024-11-01 14:28:12: 0: STDOUT: ****

2024-11-01 14:28:15: 0: WARNING: Monitored managed process 3dsmaxProcess is no longer running

2024-11-01 14:28:15: 0: Done executing plugin command of type 'Render Task'

[Joelaff]

Does this happen on multiple machines. Could be bad memory (or memory running too high a clock speed).

[Dman3d]

Multiple machines, just about everything in the farm ~120 nodes

[Dman3d]

Does anyone have latest MAX24, Vray 6 and FP 8.2.6that can test it as well? See if you get any errors?

[Dman3d]

This is buried in the logs

2024/11/06 04:37:58 ERR: [13380] [03684] [V-Ray] Building Embree Voxel Tree failed: [EmbreeTree<0,1,class VUtils::StaticTreeDelegateParam,struct VUtils::SimpleStaticTriangle,struct VUtils::SDTreeBunchDelegetorFace>::build] 1: Creating new scene failed

[Dman3d]

This does indeed to appear to be a network/switch problem. We had, for whatever reason, 10Gb switches with 1Gb connections from each to the server. They are now replaced with 20Gb/10Gb and the problem vanished.
Noticed to on 2 machines only there was never an error, when 3 or more much less 100 errors.
My guess was when the vrmeshes would load there was a limit, quota or otherwise scrum at the server/network level. Then only parts got loaded or something like that then would fail.
I do not know what else IT may have done but there was mention of a drive access issue of some sort which may or may not have played a role as someone mentioned earlier about NAS configuration. So could be either config, switches or both.

This all made jobs sort of tumble through the farm where error, error, error, render, error, render, error, error randomly on each machine. My guess is was some jobs tried to load on machines at roughly the same time.

[Dman3d]

The switches did not resolve this. It only changed the error. The vrmesh message went away but an error when render would start became clear.
Dug into it more and IT had set to no paging on windows for some reason and most of the machines were running out of virtual mem on swap. Setting to windows managed seems to have actually cleared it.
Smh, never occurred to me anyone would do that. Will update if changes. I feel confident this was the issue. So far test on one machine show the error gone.

[Joelaff]

Thanks for the update. Yeah, as tempting as no paging sounds I have never enabled it, even in machines with 512GB of RAM.