Thomas Ericsson wrote:
> [posted to rush.general]
>
> I get this while rendering on some XP-boxes (both sw and mr).
> Rendering locally does not seem to generate the same problem. We got
> Maya 8.5 SP1 installed on the machines. Seems like a maya problem,
> but I was hoping someone could shed a light on this.
>
> Executing: Render -r sw -proj //Tubby/Data4/XXX_XX_Fido_Development/
> maya/ALCOHOL -s 101 -e 105 -b 1 //Tubby/Data4/XXX_XX_Fido_Development/
> maya/ALCOHOL/scenes/05_RND/Alko_Toon_RND.ma
>
> Starting "C:\Program\Autodesk\Maya8.5\bin\mayabatch.exe"
> // Maya exited with status -1073741502
Hi Thomas,
What I'd do is login as the user the rushd service is configured
to run as on this machine [see the "RunningAs:" line from the frame log
to determine which user that is] and try copy/pasting that command into
a DOS window to see if you can replicate, or if any weird dialogs
pops up (ie. DLL errors or some such)
The negative exit code "-1073741502" coming back from maya
is likely causing the "Can't spawn/No such file or directory" error
message from Perl, which you can ignore:
> Can't spawn "Render -r sw -proj //Tubby/Data4/XXX_XX_Fido_Development/
> maya/ALCOHOL -s 101 -e 105 -b 1 //Tubby/Data4/XXX_XX_Fido_Development/
> maya/ALCOHOL/scenes/05_RND/Alko_Toon_RND.ma": No such file or
> directory at //Bandit/Bandit/RUSH_Renderscripts/.common.pl line 250.
..that message is a known bug in activestate perl's system()
command, eg:
http://bugs.activestate.com/show_bug.cgi?id=60738
http://bugs.activestate.com/show_bug.cgi?id=45337
..so just ignore that 'Can't spawn/No such file or directory'
message, it's spurious and misleading.
> Also, when maya crashes it triggers senddmp.exe and this program does
> not exit by itself, so after X number of crashes we have X number of
> senddmp.exe spawned each claiming roughly 3 MB of RAM. I'm thinking I
> should just remove or rename this little program.
Possibly this article has useful info:
http://discussion.autodesk.com/thread.jspa?threadID=505234
One thing probably worth trying in that article is the recommendation
to set the REPORTERROR environment variable to zero, eg. in the WINDOWS
section of the submit script, try adding:
$ENV{REPORTERROR} = 0;
..as that might prevent the starting of senddmp.
Since I can't replicate the problem here, you might try that
before trying to fix the problem, just to see if that helps
in preventing senddmp.
If it does, I'll put that environment variable setting as a default
in the submit-maya scripts.
Do follow up here if you have any progress.
[01/29/08: Added info about checking for the 'RunningAs:' line in frame log -erco]
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|