[zoppo]

Uh Oh - one more!

My 20th screenshot today!

The Monitor suddenly stopped updating and showed this:



After a restart the Monitor worked again.

Manager and Nodes are still working.


EDIT: Awwwwww ... it was my 21st screenshot

EDIT2: HEYYYYYY PAGE 4! Huzzah!

[zoppo]

Any news on why a Node that clearly has access (even via UNC) to the MXS files does not use them?

Or why he suddenly can access them after being restarted?

[Bubbaloo]

Maybe it's time for you to hire an I.T. staff that knows more about networks than you.

Oh, did that make me sound like an asshole? Well, I guess I'm in the right place.

[zoppo]

Oh, did that make me sound like an asshole?

Yes.

[Bubbaloo]

Congratulation - I've done it again.

[zoppo]

If you wish to further discuss whether you

a) sound like an asshole or not or if you

b) indeed are an asshole or not

please open your own thread and stop spamming mine.


Here I try to get MW3 to do what MW2.7 already could.

[eric nixon]

I think that the best for the moment, for you and your company,..is to roll back to 2.7 to save you too much stress, you can still have mw3 installed for testing (works on windows)

OR keep testing for the general benefit of our community?

[Fernando Tella]

A couple of things that crossed my mind:

Does your NAS has some kind of firewall integrated?

and

Are you testing with a V3.0 scene?

[zoppo]

I think that the best for the moment, for you and your company,..is to roll back to 2.7 to save you too much stress, you can still have mw3 installed for testing (works on windows)

My next projects all are Vray, so I'm safe there. But I thought I would use the time to get MW3 to do what I bought it for.
Thanks for the suggestion. Maybe I will do a parallel installation.

OR keep testing for the general benefit of our community?

Well, I have spent nearly three days now trying and testing and documenting.
I have posted 30 posts and close to 50 screenshots.
As I wrote I try to document every step I take and every result I get.
Of course I do this not only for me but for others who might run in similar problems.

At the moment I am a bit baffled because contrary to what "some people" think I worked a few years as windows and windows network support guy. So I know most of this stuff.
I try things like moving the shared drive from the NAS to another machine or using UNC paths or starting the manager on another machine. As mentioned earlier my network works flawless with Vray DR, Teamrender DR, Teamrender animation, Netrender animation, MW2.7 and so on.

Now I need new input from NL. I have written down some question and I have in detail shown how I got to them.

[zoppo]

A couple of things that crossed my mind:
Does your NAS has some kind of firewall integrated?
Are you testing with a V3.0 scene?

Thanks for asking.

No, the NAS has no firewall. It is this one http://www.readynas.com/?p=6167
Anyway to exclude it as a source of error the NAS was no longer involved in my latest tests. All data was on a shared windows drive.
And 4 of the clients rendered as they should - 5 did not. They "waited" for a file they clearly had access to. See my screenshots on page 2.

and

The scene was originally set up in Cinema4d with MW2.7 but it was exported with the latest MW3 plugin.
It perfectly opens in Studio and 4 of the clients did render it. The 5 others had to be restarted. After the restart they did render it too, so I think the scene is ok.

[Mihai]

zoppo, I think you'll never get any progress "debugging" things in this manner. For what it's worth, I would proceed more like this, and these are the questions I'd ask myself:

Before doing anything else:

1. Quit all network components, including Manager, Monitor and all nodes.
2. Restart Manager and go to File>Purge temp files. This makes it sure that there aren't any older jobs interfering with a new job after all this testing.
3. Restart Monitor and purge its temp files.
4. Restart ONLY ONE NODE, on one of the computers that don't start rendering.

Have you tried with any other scenes, or just this particular one?
If you try with a new simple scene and on this node that didn't start before, does it render ok?
If not, check this node is properly licensed, does Maxwell render ok on it?

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.

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.

[zoppo]

zoppo, I think you'll never get any progress "debugging" things in this manner. For what it's worth, I would proceed more like this, and these are the questions I'd ask myself:

...

I will try this but there is one problem: There is no "node that doesn't start". Some nodes that did not start on my test on page 3 did indeed start on my test on page 2. And they all are licensed properly.

But I will try your suggestions step by step in the next days. And there will be screenshots

[zoppo]

quote="Mihai"
1. Quit all network components, including Manager, Monitor and all nodes.

Done

2. Restart Manager and go to File>Purge temp files. This makes it sure that there aren't any older jobs interfering with a new job after all this testing.

Done

3. Restart Monitor and purge its temp files.

Done

4. Restart ONLY ONE NODE, on one of the computers that don't start rendering.

Done. Purged its temp files too.

Have you tried with any other scenes, or just this particular one?

No, trying just now. A few simple shapes, sky and sun, standard materials, only one texture.

If you try with a new simple scene and on this node that didn't start before, does it render ok?

Yes. At least it starts. I have to see how it is after a few more frames. If it freezes again / doesn't read the texture any more and so on.

If not, check this node is properly licensed, does Maxwell render ok on it?

It is and it does. But that was true yesterday also.

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.

Will do.

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.

[zoppo]

And the node in question still shows this second MW cmd window:



What (and why) is that?

[zoppo]

The node rendered without a problem to frame 41.

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