[zoppo]

If it does render ok, start now only the other nodes that didn't render before.
Purge their temp files.
Now start rendering this same simple scene on all these previously non working nodes.

They are working.
The monitor stopped updating after frame 27.
After restarting the monitor it worked again.

I started one of the five node while the others were already rendering.
This node was registered again with its IP address.
It is rendering now under its name but the frame it started under its IP stays in the job list "running".

If you get to here, let us know. Then, and only then, start the other nodes that were working before, and try a more complex scene.

I will now try the simple scene with all nodes.

[Mihai]

Ok great, so to recap this last part (doing this especially for Juan so he can see a quick summary and problems of your last posts):

1. Starting only Monitor, Manager and one Node:
"the node in question still shows this second MW cmd window:"
http://www.maxwellrender.com/forum/view ... 21#p376821

Does only this particular node show that cmd window, or all the others as well?

2. Node rendered all the frames of the new test scene ok, but:

The monitor had stopped updating at frame 19.
After restarting the monitor it worked again.

3. Start now only the other nodes that didn't render before

They are working.
The monitor stopped updating after frame 27.
After restarting the monitor it worked again.

Also, problem when adding a node when a job is already running:

I started one of the five node while the others were already rendering.
This node was registered again with its IP address.
It is rendering now under its name but the frame it started under its IP stays in the job list "running".

[zoppo]

I restarted all nodes, I purged all temp folders.

I started the simple scene.

5 nodes are rendering, 4 are "waiting".

1 of them is a node that rendered fine in the last test.

This node just crashed, the other 4 are rendering.

I stopped the job.

1 of the rendering nodes refuses to stop.


----

Restart all. Purge all.

The simple scene works with all nodes ATM.


----

Question: How many network I/O connections are opened per node?

[zoppo]

Ok great, so to recap this last part (doing this especially for Juan so he can see a quick summary and problems of your last posts):

1. Starting only Monitor, Manager and one Node:
"the node in question still shows this second MW cmd window:"
http://www.maxwellrender.com/forum/view ... 21#p376821

Does only this particular node show that cmd window, or all the others as well?

It took me a moment to realize the other points weren't questions.

Regarding your question:

ATM no node is showing it.

Before always one or two were showing the CMD, not necessarily always the same ones (after a restart).

----

The nodes are still rendering. The monitor stopped updating after they each had rendered ~ 4 frames.
But the nodes are still rendering and writing the MXIs without a UNC path.
BTW I am rendering to my shared windows drive, not to the NAS.

[zoppo]

After some time I got to testing again.

The nodes are rendering now although I changed nothing in the network setup.
I get some crashes here and there. Nothing too serious.

Monitor still stops updating after some time. Restarting it fixes this.

The problem about the manager not realizing when a node has crashed and / or handling the newly started node under its IP is still there.

Some of the nodes still show this. But it is always a different node.



BTW: Afaik I can't change the thread's title which stems from my initial frustration. Maybe it should be changed to something like "Node / license [solved] and various other network problems"