Dispatcher not giving nodes next chunk set

Viewing 2 posts - 1 through 2 (of 2 total)
  • Back to forum
    Posted in: Muster usage
  • Nathaniel
    3rd May 2007 at 5:31 pm #14176

    The problem I am experiencing is with scene files at random. When the problem occurs it will be only with one scene file while others execute fine. The ones that work will never experience the problem below and the scene files that have problems always have this problem with 5.x.

    The problem: When the chunks are submitted to any one of the the 6 rendernodes and completed the node’s text in the dispatcher turns red and the j field (two fields from the Host Instance Name) turns the ball red and the node never receives a new chunk from the dispatcher.

    So if I have 4 frames in a chunk only 24 frames of the scene are rendered and all the nodes are hung in this way. The logs for the chunks show no warnings/errors. I have taken the two chunks commandlines (ex: rendering frames 1-4,5-8) given to the nodes and manually executed them in a batch file on the rendernode while logged in as the service. They return without errors as well and both chunks are executed.

    I’m currently running M-5.12 & Maya 8.0

    Leonardo Bernardini
    22nd May 2007 at 12:05 am #14658

    The Muster behaviour is normal. If it detects an hard error in the job, it adds the job to the temporary client EXCLUSION LIST and do not process it further. The feature has the purpose to avoid keeping nodes with faulty scenes.

    If the scene fails at random, you should locate the render log PACKET of that particular chunk that caused the exception and locate the reason of the problem.

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

You must be logged in to reply to this topic.