stuck on mayabatch

This topic contains 4 replies, has 2 voices, and was last updated by  bernie 2 months, 2 weeks ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • 3rd May 2019 at 7:52 pm #17486

    Hello, I’m trying to setup muster templates for maya and I can’t even get maya software properly:

    [MUSTER]Spawning process C:\Program Files\Autodesk\Maya2018\bin\Render.exe inside C:\Program Files\Autodesk\Maya2018\bin using the following command line flags:
    [MUSTER]-r sw -n 0 -proj "Q:\PROJECT\muster\muster_testproj" -rd "Q:\PROJECT\muster\muster_testproj\images" -s 1.000 -e 1.000 -b 1.000 -rfs 1 -rfb 1 -pad 1 -preRender "system(\"net session\")" -verb "Q:\PROJECT\muster\muster_testproj\scenes\renderfile_sw.mb"
    
    Locale is: "French_France.1252(0x040c) (LCID:0x040c)"
    // Using temp file "C:\Windows\TEMP\ASTEC651632.tmp"
    
    ////////////////////////////////////////////////////////////////////////////
    // Starting Mel program
    
    proc renderIt(string $name) {
    
    string $opt = ""; string $rl=""; string $rp=""; float $resize=-1.; int $interactive=0; select defaultRenderGlobals; setAttr .renderAll 1; // Before all flags
    
    setAttr .numCpusToUse 0; if(!<code>about -mac</code>) { threadCount -n 0; }; // For flag -n
    
    workspace -fr "images" "Q:\\PROJECT\\muster\\muster_testproj\\images";workspace -fr "depth" "Q:\\PROJECT\\muster\\muster_testproj\\images";; // For flag -rd
    
    removeRenderLayerAdjustmentAndUnlock .animation; setAttr .animation 1; removeRenderLayerAdjustmentAndUnlock .startFrame; setAttr .startFrame 1.000; // For flag -s
    
    removeRenderLayerAdjustmentAndUnlock .animation; setAttr .animation 1; removeRenderLayerAdjustmentAndUnlock .endFrame; setAttr .endFrame 1.000; // For flag -e
    
    removeRenderLayerAdjustmentAndUnlock .byFrameStep; catch(<code>setAttr .byFrameStep 1.000</code>); // For flag -b
    
    removeRenderLayerAdjustmentAndUnlock .modifyExtension; setAttr .modifyExtension 1; removeRenderLayerAdjustmentAndUnlock .startExtension; setAttr .startExtension 1; // For flag -rfs
    
    removeRenderLayerAdjustmentAndUnlock .byExtension; catch(<code>setAttr .byExtension 1</code>); // For flag -rfb
    
    removeRenderLayerAdjustmentAndUnlock .extensionPadding; catch(<code>setAttr .extensionPadding 1</code>); // For flag -pad
    
    removeRenderLayerAdjustmentAndUnlock .preMel; catch(<code>setAttr -type &quot;string&quot; .preMel &quot;system(\&quot;net session\&quot;)&quot;</code>); // For flag -preRender
    
    setMayaSoftwareLayers($rl, $rp); setImageSizePercent($resize); mayaBatchRenderProcedure($interactive, "", "", "mayaSoftware", $opt);; // After all flags
    
    			}
    			
    			//
    			// Main part
    			//
    			
    			string $sceneName = "Q:\\PROJECT\\muster\\muster_testproj\\scenes\\renderfile_sw.mb";
    			
    			int $checkScene = <code>file -q -ex</code>;
    			string $checkSceneName = <code>file -q -sn</code>;
    			if (!(($checkScene==1) || ($checkSceneName!=""))) {
    				quit -abort -force -exitCode 209;
    				error ("Cannot load scene \""+$sceneName+"\". Please check the scene name.");
    			} else if (catch(<code>renderIt($sceneName)</code>)) {
    				quit -abort -force -exitCode 210;
    				error ("Scene "+$sceneName+" failed to render.\n");
    			} else {
    				print ("Scene "+$sceneName+" completed.\n");
    				quit -abort -force -exitCode 0; // Exit Maya
    			}
    			
    			// Ending Mel program
    // Maya file is "Q:\PROJECT\muster\muster_testproj\scenes\renderfile_sw.mb"
    
    Starting "C:\Program Files\Autodesk\Maya2018\bin\mayabatch.exe"
    Arg[1]="-batch"
    Arg[2]="-file"
    Arg[3]="Q:\PROJECT\muster\muster_testproj\scenes\renderfile_sw.mb"
    Arg[4]="-script"
    Arg[5]="C:\Windows\TEMP\ASTEC651632.tmp"
    Arg[6]="-proj"
    Arg[7]="Q:\PROJECT\muster\muster_testproj"
    

    There’s a prerender mel to see if I was launching in Admin mode which I figured out is troublesome for drive mapping but it isnt being called I’m stuck on Starting “C:\Program Files\Autodesk\Maya2018\bin\mayabatch.exe” if I don’t use the -verb mode.

    The client is being run as a service, it works by batching locally with .bat files and the similar command.

    Any ideas or hints for debugging are welcomed.

    I’ve also tried UNC mapping \\192.168.0.xx instead of drive letters but it doesn’t change anything.

    3rd May 2019 at 8:10 pm #17487

    Hi Bernie,

    First of all, what Muster version are you using ? you posted into the Muster 8 forum , so maybe I’ll move this topic later.
    Then, you have to check the following things:

    1) An user is assigned to the Renderclient service, if it’s running in LOCAL SYSTEM ACCOUNT, Maya batch and network connections may not work

    2) Start a simple scene first, without using drive mappings, neither pre-render mel scripts and from a network location

    3) Once you get a successfull render, configure the drive mappings inside the Renderclient preferences (from console, right click on a node and then select Configure , then locate the Drive mappings sections), and then restart (or soft-restart from the console context menu) the render client

    A stuck maya batch 99% of case is due to a wrong user configuration, so I suppose you have not assigned an user to the service.

    Let me know if this helps you

    6th May 2019 at 10:13 am #17489

    Thanks for the quick reply. We are on 8.6.1

    A simple ‘batch’ job works (ie echoing works, at least shows up in the log and exits gracefully)

    However a simple maya (software) job simply ‘hangs’ and never returns; both Render.exe and mayabatch.exe are active on the client machine, but not doing anything. I tried it with a .bat file locally and the job renders fine in a few seconds.

    Here is the renderclient log:

    05/06/2019 10:04:14 - [Core] Accepting new management connection(1416) from 192.168.0.202:10480
    05/06/2019 10:04:30 - [Core] Management connection(192.168.0.202:10480) closed by remote host
    05/06/2019 10:06:43 - [1] Job process terminated with exit code 1
    05/06/2019 10:07:39 - [1] Streaming log to C:\Program Files\Virtual Vertex\Muster 8\logs\client\processes\1557130055.2697.1.N9.001_0002_sw_test
    05/06/2019 10:07:39 - [1] Starting job executable C:\Program Files\Autodesk\Maya2018\bin\Render.exe with commands: -r sw -n 0 -proj "\\192.168.0.21\PROJECT\muster\muster_testproj" -rd "\\192.168.0.21\PROJECT\muster\muster_testproj\scenes\images" -s 1.000 -e 1.000 -b 1.000 -rfs 1 -rfb 1 -pad 1 -preRender "system(\"net session\")" "\\192.168.0.21\PROJECT\muster\muster_testproj\scenes\renderfile_sw.mb"
    05/06/2019 10:07:43 - [1] Real job process running with PID 3420
    7th May 2019 at 9:13 am #17491

    So you’re problem is only with Maya, I see also that you’re using Maya 2018 and honestly this is not certified with Muster 8.6.1 that’s a very old version.
    By the way, if a CMD prompt works, try to stop the Muster render client service, and start the renderclient.exe manually in console mode, then re-try to send the job. If it works in this way, the problem is with your service configuration.

    7th May 2019 at 4:06 pm #17492

    I’m not in charge of buying licences sorry.

    It appears it is a mix between file permission issue and drive mapping

    I’m writing this here if anyone as a similar problem, this is how I fixed it:

    – Using the ‘normal’ client mode (that pops up a window – High Debug) instead of a service (even with a given user and password)
    – Hardcoding the network mapping in (Q:\ to \\192.0.0.xx\folder) in the dispatcher clients config

    I had issues where the written files wouldn’t even be available for opening/browing. I guess it is because we (client machines) are ‘admin’ users in our sessions (bad idea I think but I’m not in charge of IT).

    The jobs launch with a thousand errors and it’s red all over but they render which is what I wanted.

    It’s a maya-sw modified to work with octane.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.