#Network bug??
13 messages in this thread
What would cause the network log to do the following:
[13:06:34] ———————————
[13:06:34] Machine 0003 [BON-486/66-32MB] Errors:
[13:06:34] Render cancelled by ESCAPE
[13:06:34] ———————————
[13:06:34] Machine 0003 [BON-486/66-32MB] failed on frame 751
[13:06:34] Marking machine 3 as failed due to logged anim errors
[13:06:36] Creating cmd file for machine 3, process "H-BON04"
The last line seems to be the problem! For some reason, when we escape during
a slave session, it creates a cmd file to start the next process in line, even
though we have exited from the slave mode!!
That causes the next process in line to report that machine X is "running" in
the queue even though it's not even in slave mode.
We have 6 machines that run in slave mode daily and the problem occurs on them
all. We are using the default settings in the 3DSNET.SET file and ALL machines
run R4. Any ideas?
– Steve Ormonde
I've seen similar network behavior.
Perhaps this is related to what is described on page 29 of the User's Manual.
It says that to exit slave mode you press <esc>, but if you ran 3DS SLAVE from
the command line, you need to press <alt><esc> to return to the command line.
I haven't actually compared the two, but give it a shot.
– Dave
>> but if you ran 3DS SLAVE from the command line, you need to press
<alt><esc> to return to the command line <<
You're probably right! We'll start using alt-esc and see what happens.
You'd think that the standard esc key would be disabled when run from the
command line if it's gonna cause problems though…
Thanks for the help!
– Steve Ormonde
> [13:06:36] Creating cmd file for machine 3, process "H-BON04" <
Uh, I think this is a feature. I'm under the impression that it happens
whenever a process is interrupted, regardless of how or why. I think the idea
is to keep the slave working on other processes in the queue even if it fails
on the current one. Doing this does seem strange in the context of the ESC
key.
— James — Choreo Motion —
James,
See the reply from David. I'm gonna try using alt-esc and see if the problem
goes away.
– Steve Ormonde
<< The last line seems to be the problem! For some reason, when we escape
during a slave session, it creates a cmd file to start the next process in
line, even though we have exited from the slave mode!!>>
Steve,
Are their any IPAS routines or other External processes (i.e. .BAT files) in
the project file? And are you Rendering from the Viewport or from Video Post?
-Brian
Hi Brian,
>> Are their any IPAS routines or other External processes (i.e. .BAT files)
in the project file? And are you Rendering from the Viewport or from Video
Post? <<
We have one custom IPAS routine we use for quickly changing between scenes, no
external processes and we render from the viewport.
But, the problem has gone away. Using ALT-ESC when canceling a command line
slave mode is a MUST. The problem we were having (we think) was due to
pressing ESC only.
Perhaps, future versions won't have this requirement…
– Steve Ormonde
<< But, the problem has gone away. Using ALT-ESC when canceling a command line
slave mode is a MUST. The problem we were having (we think) was due to
pressing ESC only.>>
Odd. But I will make a note of this.
-Brian
Just an update on the alt-esc vs. esc issue:
After several days of in and out of slave mode on 6 systems, using alt-esc
when launched from the command line to exit slave mode, our "machine x running"
problem has gone away.
In addition, if a system was accidentaly exited by esc only, the system would
appear as running in the queue. By reentering slave mode _from the command
line_ and exiting properly (alt-esc), the "machine x running" message would go
away. An interesting side note; if a command line slave machine was
accidentaly exited by esc, set into slave mode _from within 3DS_, and exited by
esc, the "machine x running" would still appear, FWIW.
– Steve Ormonde
Hi Steve,
<< After several days of in and out of slave mode on 6 systems, using alt-esc
when launched from the command line to exit slave mode, our "machine x running"
problem has gone away. >>
Glad to hear that the program is operating correctly. As an aside, this alt-esc
is documented in pg 29 of the User's Guide as the last sentence in the Netword
Menu Functions/Slave section. ;-}
jonas[adesk]
Jonas,
>> As an aside, this alt-esc is documented in pg 29 of the User's Guide as the
last sentence in the Netword Menu Functions/Slave section. <<
Yes, I did read it too.
Not to beat a dead horse or anything, but esc and alt-esc both get you out of
command line slave mode. Perhaps, as a wishlist item, esc can be the standard
exit. After a weekend of rendering, it's not always possible to know which
machine was slaved by command line or within 3DS.
Thanks,
– Steve Ormonde
<<..wish.. >>
got it.
<< After several days of in and out of slave mode on 6 systems, using alt-esc
when launched from the command line to exit slave mode, our "machine x running"
problem has gone away.>>
Steve,
Yes, in fact this is even documented in the Adv users Guide, as Jonas pointed
out. That slipped by me.
-Brian