Hi
use Deadline 3.1. Maya2009.
render Progress is 100% but not finish rendering.not outout renderimage.
Slaves repeats reading texture. 
thanks for any help
-ex12r
Slaves repeats Messageā¦
A state does not change.
no error.but not finish renderingā¦
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 35 MB for module JOB, now: 588 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 33 MB for module JOB, now: 567 MB
0: STDOUT: MEM 0.13 progr: scene cache flushed 1 MB in 0.00s, now: 615 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 33 MB for module JOB, now: 584 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 16 MB for module JOB, now: 595 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 71 MB for module JOB, now: 551 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 46 MB for module JOB, now: 500 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 16 MB for module JOB, now: 649 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 16 MB for module JOB, now: 655 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 70 MB for module JOB, now: 583 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 16 MB for module JOB, now: 634 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 30 MB for module JOB, now: 623 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 14 MB for module JOB, now: 600 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 20 MB for module JOB, now: 629 MB
0: STDOUT: MEM 0.12 progr: scene cache flushed 9 MB in 0.00s, now: 631 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 16 MB for module JOB, now: 620 MB
0: STDOUT: MEM 0.12 progr: scene cache flushed 3 MB in 0.00s, now: 620 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 17 MB for module JOB, now: 601 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 59 MB for module JOB, now: 551 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 50 MB for module JOB, now: 503 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 57 MB for module JOB, now: 540 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 33 MB for module JOB, now: 510 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 17 MB for module JOB, now: 554 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 19 MB for module JOB, now: 544 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 14 MB for module JOB, now: 595 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 44 MB for module JOB, now: 600 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 17 MB for module JOB, now: 600 MB
0: STDOUT: GAPM 0.5 progr: scene cache flushed 1 MB in 0.00s, now: 630 MB
0: STDOUT: MEM 0.5 progr: scene cache flushed 1 MB in 0.00s, now: 615 MB
0: STDOUT: MEM 0.5 progr: scene cache flushed 1 MB in 0.00s, now: 613 MB
0: STDOUT: MEM 0.5 progr: scene cache flushed 1 MB in 0.00s, now: 619 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 14 MB for module JOB, now: 622 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 28 MB for module JOB, now: 627 MB
0: STDOUT: MEM 0.14 progr: scene cache flushed 1 MB in 0.00s, now: 636 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 98 MB for module JOB, now: 524 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 18 MB for module JOB, now: 507 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 20 MB for module JOB, now: 510 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 20 MB for module JOB, now: 549 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 44 MB for module JOB, now: 564 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 18 MB for module JOB, now: 587 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 32 MB for module JOB, now: 581 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 71 MB for module JOB, now: 527 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 47 MB for module JOB, now: 535 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 16 MB for module JOB, now: 493 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 13 MB for module JOB, now: 724 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 16 MB for module JOB, now: 707 MB
0: STDOUT: PHEN 0.11 progr: scene cache flushed 2 MB in 0.00s, now: 691 MB
0: STDOUT: MEM 0.11 progr: scene cache flushed 13 MB in 0.00s, now: 673 MB
0: STDOUT: MEM 0.3 progr: scene cache flushed 13 MB in 0.00s, now: 671 MB
0: STDOUT: MEM 0.11 progr: scene cache flushed 7 MB in 0.00s, now: 668 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 27 MB for module JOB, now: 644 MB
0: STDOUT: PHEN 0.3 progr: scene cache flushed 7 MB in 0.00s, now: 635 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 32 MB for module JOB, now: 619 MB
0: STDOUT: MEM 0.14 progr: scene cache flushed 13 MB in 0.00s, now: 605 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 15 MB for module JOB, now: 589 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 16 MB for module JOB, now: 606 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 46 MB for module JOB, now: 568 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 15 MB for module JOB, now: 573 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 70 MB for module JOB, now: 520 MB
0: STDOUT: MEM 0.1 progr: scene cache flushed asynchronously 30 MB for module JOB, now: 543 MB
Can you post the full slave log that contains this job? The easiest way to get a āfreshā log would be to do the following:
- Close all your Slave applications
- Resubmit this job
- Start up ONE Slave so that it can pick up the job
- Let it start the job and render it until it gets to the point where it just repeats the message you posted
- Let it run for 5-10 minutes at this point
- From the Slave, select Help -> Explore Log Folder
- Close the Slave
- Find the most recent Slave log in the log folder and post it here
This should help give us a better idea of whatās going on. Also, do you have this problem with all Maya jobs, or just this one in particular?
Cheers,
- Ryan
Thanks Ryan! 
It is not particular.only Rarely(some) job/slaves.
I try post log. Please wait a little.
Hi Ryan.
upload logfile and tasks imageā¦
It is not every time.but frequent problemsā¦
ex12r
Thanks for the log. It looks like towards the end, mental ray is swapping out memory (based on these lines of output):
Near the top of the log, I also see this:
That seems like a low number for maximum memory. Maybe mental ray is swapping and that causes the render to then take forever. This is just a guess, but maybe there isnāt enough memory for mental ray to load the textures, so it swaps and tries again, and then gets stuck in a loop. Is it possible for you to try and increase the heap size that mental ray uses? I should note that Deadline doesnāt control this value explicitly, so Iām guessing it needs to be set in the mental ray options within maya before submitting the job.
Cheers,
- Ryan
thanks Ryan!! 
I try rendering with halfsize texture.
and examine mantalray memory option.
I will post report.
thanks
-ex12r