Maxwell Render

I just installed 2.6 on my 5 nodes and ran a test render. It was all working okay (mostly) prior to that but now all the nodes failed on the merge and they all have the same basic message in the slave console:

[04/November/2011 00:40:20] Render process finished successfully!
[04/November/2011 00:40:20] Connecting to render process: Binding to port: 45464
[04/November/2011 00:40:20] TCP message from manager received.
[04/November/2011 00:40:20] Message from manager: send_mxi
[04/November/2011 00:40:20]
[04/November/2011 00:40:20] Start MXI transfer process
[04/November/2011 00:40:20] ERROR: Unable to open file for sending!
[04/November/2011 00:40:20] ERROR: File C:\Documents and Settings\Administrator\Desktop\MX_TEMPS\mxnetwork\rendernode\Jug_02_jug_only.mxi cannot be sent!
[04/November/2011 00:40:20] ERROR: File does not exist

From what I can see all the temp directories for all the nodes are empty. Any idea what is wrong?

Thanks in advance
/b

_________________
Brett Simms
http://www.heavyartillery.com

Something is very wrong atm. I think the first problem I ran into might have been that I had turned off the save image and mxi in the render output options, intending to speed up render tests, and I had assumed that the save settings in the co-op render dialog would be override those. I don't think they did

However, once I fixed that I still have the same problem:

[04/November/2011 11:36:08] Render process finished successfully!
[04/November/2011 11:36:08] Connecting to render process: Binding to port: 45464
[04/November/2011 11:36:08] TCP message from manager received.
[04/November/2011 11:36:08] RN MMG in: 112
[04/November/2011 11:36:08] Message from manager: send_mxi
[04/November/2011 11:36:08]
[04/November/2011 11:36:08] Node Sending MXI file to manager:
[04/November/2011 11:36:08] Start MXI transfer process
[04/November/2011 11:36:08] Connection for sending MXI file established
[04/November/2011 11:36:08] ERROR: Unable to open file for sending!
[04/November/2011 11:36:08] ERROR: File D:\Maxwell_temps\mxnetwork\rendernode\Jugs_05_Purex_bottle_Only.mxi cannot be sent!
[04/November/2011 11:36:08] ERROR: File does not exist


All nodes show an empty temp directory and there is nothing in the manager's temp directory. I have tried running the manager with two different shared directories and on two different machines with the same result. Any help please?

_________________
Brett Simms
http://www.heavyartillery.com

Turned everything off, reset all the temp folders, restarted everything and now I think it's working okay. Either that fixed it, or perhaps I didn't re-activate the save image buttons after all. In any case, all good atm.

/b

p.s: it would be good to make sure that the "save image" and "save mxi" flags are turned on with every co-op render no matter what it's set to in the mxs. I cannot see any use for co-op rendering where that doesn't happen, and it will save a lot of wasted time/heartaches for some of us who tend to forget to turn stuff like that back on

_________________
Brett Simms
http://www.heavyartillery.com

Actually - there is a much bigger problem going on here that is the reason for this: co-op rendering is deleting the mxs file on completion of the render. I'll post a separate thread to make sure others see it and don't lose work like I did.

b

_________________
Brett Simms
http://www.heavyartillery.com

But Network first copies your MXS file to a temp folder, and deletes that after the render is done. Do you mean it actually deletes your original MXS file? How do you have the temp folders set up?

_________________
Next Limit Team
Merchant of happiness

Mihai, I have also seen this happen when I send to network from Max. After the job is done, it deletes the exported MXS file from the defined save location. Only the saved image and MXI are left.

_________________
Brian Looney
Maxwell + RealFlow
http://lunatic-studio.com/
Help! I'm dispersing into a haze of probability!

Hey Mihai -
It deletes the master mxs file, not the temp one (or rather, it deletes both). It's a bit of an issue

_________________
Brett Simms
http://www.heavyartillery.com

Hi, I'm having the same issue with the same "ERROR: Error binding render node to port:" and "Tcp server can not listen port:" messages. After the 2.6 upgrade, the rendernodes no longer find my computer/IP address (pinging can't connect). I've tried everything, even reinstalling Maxwell and it's definitely a TCP issue- my network is fine in all other non-Maxwell related regards. The thing is, if I reset my IP address connection and restart my computer, my Render Node license and Manager connect to the nodes before I run a job (no error messages in the log). The minute i try and process a job by sending an MXS to the nodes, it gives me the error message and can no longer find the nodes.

Has anyone found a solution to this?

Since coworkers of mine don't have this issue and they are using Windows 7 while I'm using Windows XP 64, I'm wondering if it's an XP bug.

Is that network issue solved ?

Because i'm still waiting to install 2.6 on all my PCs...

_________________
Claudio 'Naxos' gallego, CG artist and teacher...
http://www.chromelight-studio.fr
"1+1=3... for large values of 1"
"Circle is the fastest way from a point to itself"

These issues have been fixed for the next update coming in January, but regarding the issue of port binding did you try first a few network renders with all firewalls off to make sure that's not interfering with Network?

_________________
Next Limit Team
Merchant of happiness

I did not install 2.6 yet, since i'm quite always in production and everything works well now in 2.5.x...

i'm waiting to be sure i can go to 2.6.x before i install...

_________________
Claudio 'Naxos' gallego, CG artist and teacher...
http://www.chromelight-studio.fr
"1+1=3... for large values of 1"
"Circle is the fastest way from a point to itself"

This is kinda late, but I ran into a bug like this. I had turned off the option to save an mxi and it gave me the same error you were getting. once I turned on the option to save an mxi, it fixed the issue. Not sure if it's been fixed in 2.61 or not.

_________________
www.justingoode.com