Spawner dropping down

[PIXELBOX_SRO]

Hi guys,
recently we have the spawner dropping down.
We start a job but one machine starts spawner but within a minute it closes down.
Any idea what could it be?
Cheers
M

[PIXELBOX_SRO]

of course firewalls are off

[3dcrgr]

Hi guys,
recently we have the spawner dropping down.
We start a job but one machine starts spawner but within a minute it closes down.
Any idea what could it be?
Cheers
M

I have the same problem but it depends on the scene.
Some scenes it render fine and some scenes the render node crashes.
Could it be lack of RAM?

On the other side, this node was once my workstation (few months ago) and it rendered fine those scenes..

[tashko.zashev]

Hi,

Are there any errors in the V-Ray log on the slave machine ?
Also if you can provide more details about this issue will be very helpful for further troubleshooting.


Martin, what do you mean with "dropping down". Does it restart and then reload the dummy scene again or just freezes ?

I have the same problem but it depends on the scene.
Some scenes it render fine and some scenes the render node crashes.
Could it be lack of RAM?

On the other side, this node was once my workstation (few months ago) and it rendered fine those scenes..

Such symptoms could be due insufficient memory on the render node, but it could be other issue as well. The best way to see this is to track down the memory usage on the slave node or just to run a local render test. I assume that your machines are with different memory size.

[3dcrgr]

Hi,

Are there any errors in the V-Ray log on the slave machine ?
Also if you can provide more details about this issue will be very helpful for further troubleshooting.


Martin, what do you mean with "dropping down". Does it restart and then reload the dummy scene again or just freezes ?



Such symptoms could be due insufficient memory on the render node, but it could be other issue as well. The best way to see this is to track down the memory usage on the slave node or just to run a local render test. I assume that your machines are with different memory size.

For me it restarts and reloads VRaySpawner 2014 service in loops.
I have 32GB of RAM and the WS and 8GB RAM on the node.
You think its a insufficient memory problem? how can I track down memory usages? Task Manager?

[tashko.zashev]

For me it restarts and reloads VRaySpawner 2014 service in loops.
I have 32GB of RAM and the WS and 8GB RAM on the node.
You think its a insufficient memory problem? how can I track down memory usages? Task Manager?

Yes, you can use Task manager (locally on this machine or via remote connection) or you can also try to run the scene locally on this node (if it's possible at all).
Can you post the V-Ray log file from the salve machine as soon as you get this issue ?

From your description and the system specification you have shared, I suspect that there is a memory problem.

[jackieteh]

Hi,

Do you tick "Restart slaves on render end" in the Distributed rendering setting?
It solve my problem.

[3dcrgr]

Yes, you can use Task manager (locally on this machine or via remote connection) or you can also try to run the scene locally on this node (if it's possible at all).
Can you post the V-Ray log file from the salve machine as soon as you get this issue ?

From your description and the system specification you have shared, I suspect that there is a memory problem.

I just purchased and installed new 32GB RAM in the node. Unfortunately it is already rendering and I don't want to interrupt the process.
Is there a way to force the node to kick in?

edit:

Thank you for your help, the additional ram solved the problem!

[tashko.zashev]

I just purchased and installed new 32GB RAM in the node. Unfortunately it is already rendering and I don't want to interrupt the process.
Is there a way to force the node to kick in?

edit:

Thank you for your help, the additional ram solved the problem!

Thank you very much for your update.

Is there a way to force the node to kick in?

If you have this node added to the DR list at the start of the rendering process, then it can be involved in the rendering process later. You just need to start V-Ray spawner on this node.
Actually we have prepared some improvements about that for the next service pack.

[PIXELBOX_SRO]

Hi Tashko,
for me the node just closes and nothing happens.
No restart nothing. The machine has 64GB RAM so its not the ram thing
I am reinstalling the whole machine to see if it helps.
M

[tashko.zashev]

Hi Tashko,
for me the node just closes and nothing happens.
No restart nothing. The machine has 64GB RAM so its not the ram thing
I am reinstalling the whole machine to see if it helps.
M

Hi Martin,

What do you mean with "dropping down". Does it restart and then reload the dummy scene again or just freezes ?
Does it happen on particular scene only?
Can you post the V-ray log file from the slave as soon as this issue happens?

[PIXELBOX_SRO]

Hi Tashko,
it happens on all scenes unfortunatelly.
The dummy scene opens, flashes and then disappears along with the little spawner icon in the tray (right bottom corner). It doesnt reopen. and it doesnt freeze. It just closes within like 30 secs - even less
Once i install everything i will run a test and if its still doing i will send you a log for sure
Cheers!

[PIXELBOX_SRO]

Hi Tashko,
so it looks that reinstalling computer helped.
Unsure what went wrong.
We recently upgraded max to sp3, BB to new version and vray to latest stable release from the nightlies.
All comps handled the transition fine but the one
After clean windows install all seems to be running fine.
I will let you know here if i bump into any problems.
THANKS for support!
M

[tashko.zashev]

Thank you very much for the quick update Martin. I'm glad to hear that this render node is back in the business