Author Topic: Maya job fails  (Read 5656 times)


  • Full Member
  • ***
  • Posts: 13
Maya job fails
« on: June 03, 2009, 03:57:56 PM »
As well as the cmdline problem I'm having (see previous) post I'm also getting Maya Job errors:


Project Directory: /Volumes/Renderfarm/1.DAVE/1_previz
Render Directory:  /Volumes/Renderfarm/1.DAVE/1_previz
Scene File:        /Volumes/Renderfarm/1.DAVE/ball_bounce.mb

$VAR1 = bless( {
  'defaultRenderGlobals.imageFilePrefix' => 'test',
  'defaultRenderGlobals.currentRenderer' => 'mentalRay',
  'defaultRenderGlobals.outFormatControl' => undef,
  'scenefile' => '/Volumes/Renderfarm/1.DAVE/ball_bounce.mb',
  'project' => '/Volumes/Renderfarm/1.DAVE/1_previz',
  'mentalray_satellite' => 'None',
  'range' => '1-25',
  'renderDirectory' => '/Volumes/Renderfarm/1.DAVE/1_previz'
}, 'maya::Package' );

ERROR: scenefile [/Volumes/Renderfarm/1.DAVE/ball_bounce.mb] does not exist on the execution machine [render2.local] at /Applications/pfx/jobtypes/maya/ line 170.
INFO: reporting status [failed] to supe: qb::reportjob('failed')
received confirmation from worker.

Firstly, should I have some path info in the top few lines for MAYA_LOCATION etc. It's worth noting that all machines are OSX and the paths  /Volumes/Renderfarm/1.DAVE/ are accessible by the worker.

Any and all help appreciated.


Scot Brew

  • Hero Member
  • *****
  • Posts: 272
    • PipelineFX
Re: Maya job fails
« Reply #1 on: June 04, 2009, 03:58:05 AM »
The first recommendation for what to test when hitting "File Not Found" issues is to run a simple cmdline job to access that file.  That will keep it simple and isolate the issue from any jobtype complexities.

For this post, the following call can be made from the commandline:
qbsub ls /Volumes/Renderfarm/1.DAVE/ball_bounce.mb

From the QubeGUI, it can be done from Submit->Cmdline Job:
Command: ls /Volumes/Renderfarm/1.DAVE/ball_bounce.mb

Check the results in stdout for successful listing of the file.

As for OSX, it can have file mounting issues as AFS wants to mount the drives on user login, where since Qube Worker runs as a daemon, it does not have to have a user logged in.  See the Knowledge Base info at: