Maxwell Render | Official public forum

Hi, I have successfully installed the float license, and my render nodes are also connected to the license server.

But when starting up the "network manager", I get these errors (see attached screenshots).

Any tips on how I can solve this?

Thanks,

Tor M

Hi Kevron,

Could you please check that the computer with the name "Tors-Mac-Pro.local" has the IP 192.168.1.130?

While we look into that deeper as a workaround you can launch the manager doing this:

mxnetwork -multiplemanagers

so this test is skipped.

Hi,

Yes the IP is correct. I am trying to figure out how to launch the manager, is it in terminal?

Thanks,
Tor M

I have been able to open up the manager with terminal
But the Maxwell Network Monitor crashes when trying to press "next".

Its a lot like the problem in this thread: http://www.maxwellrender.com/forum/view ... 35&t=41358

It crashes before the floating dialog (the one that says the MXI path is not a network path) is visible.

Regards,
Tor M

Here is a screenshot from the Network manager. Nothing too unusual, but it is up an running.
You can also see where the monitor disconnects. That is when the crash occurs.



TorM

Kevron wrote:Hi,

Yes the IP is correct. I am trying to figure out how to launch the manager, is it in terminal?

Thanks,
Tor M

Yes, you need to open a terminal and type: Please let us know if it helps. Meanwhile we are trying to debug your problem and will let you know if this is a bug, in that case we will update a patch for you as soon as possible.

Thanks Juan,

I am going to render on a single machine tonight - and let you guys debug the problem.
I guess you will have it fixed in no time, you usually does.


Have a nice night.

Tor M

Hi Kevron,

Kevron wrote: But the Maxwell Network Monitor crashes when trying to press "next".

Its a lot like the problem in this thread: http://www.maxwellrender.com/forum/view ... 35&t=41358

It crashes before the floating dialog (the one that says the MXI path is not a network path) is visible.

Thanks for the additional info, we are looking into this.

Any closer to figuring it out?

Let me know if I should share some deep debug logs with you, or a scene file.

Thanks,
Tor M

Thanks Tor, we have almost sorted it out, we will be back to you shortly.

Great, I think the new version shaved off two hours on my render on a single machine (and that was with added volumetric too).

Looking forward to test out network render.

Cheers,
Tor M

Hi,

We have reuploaded the installers, this issue should be fixed now, please let us know otherwise.

(by the way you don't need to license the package again after reinstalling)

Sorry for the inconveniences.

Juan

Great, I will test it out tomorrow

Regards,
Tor M

I have downloaded the new install, and every nodes is updated.

I am able to start Network Manager and I have also successfully sent dependencies to all nodes.
Then, all of a sudden, the node quite one after one. And I end up with only one machine still rendering - the one who also controls the network manager.

And I cannot stop the job in Network monitor. To make it stop, I need to force quit.

Here is the log file from Network Manager: https://dl.dropboxusercontent.com/u/105 ... r_log.html

Any pointers?

I have used network rendering on Maxwell 2, and that used to work quite smooth.

Regards,
Tor M

update: I find Maxwell Network Monitor very unresponsive.
I can not add a new job. It will print:

[06/December/2013 13:28:26] New job submitted.

But nothing is really showing or happening. Same with all the commands (reset entire network, stop job and remove it from the queue, preview etc..)

Tor M