nisus Posted February 22, 2007 Share Posted February 22, 2007 Hi all, It seems that there is something wrong with the task timeout in the most recent version of backburner or SP2. My settings are set 'PER JOB' and the 'wait for max to render' is set to 64000, yet the servers always die after 600minutes. Does anyone else got this problem? Does anyone knows how to solve this? rgds, nisus Link to comment Share on other sites More sharing options...
nisus Posted February 23, 2007 Author Share Posted February 23, 2007 No one? Link to comment Share on other sites More sharing options...
Eric Posted February 24, 2007 Share Posted February 24, 2007 I recently (just a few days ago) experienced this very same thing. I was using Max with VRay. The scene I was rendering typically took about 30 hours to render (don't ask...). I had several different versions to render, so I stacked them up in Backburner and went to sleep for the night. 600 minutes later, it timed out. grr... Link to comment Share on other sites More sharing options...
nisus Posted February 26, 2007 Author Share Posted February 26, 2007 That makes at least two of us.... Can't believe there are any more people... Can anyone help us? rgds, nisus Link to comment Share on other sites More sharing options...
nisus Posted February 26, 2007 Author Share Posted February 26, 2007 **moved this trhead from MR to 3dsmax because it seems non-MR related** Link to comment Share on other sites More sharing options...
nisus Posted February 27, 2007 Author Share Posted February 27, 2007 no one??? Link to comment Share on other sites More sharing options...
Chad Warner Posted February 27, 2007 Share Posted February 27, 2007 I've had the same problem, but can't offer a solution. We just had to figure out how to get the scene to render. Link to comment Share on other sites More sharing options...
nisus Posted February 27, 2007 Author Share Posted February 27, 2007 Well, my workaround for now is DBR... unfortunately... when the image is at 99.99% it means that all but ONE machine in the network is not being used... My last image rendered in about 1,5hour, but I am still waiting for the image to get saved... for 4,5hours already!!! The server states 99.99%, the max dialog 100%... but nothing moves... irritating!! rgds, nisus Link to comment Share on other sites More sharing options...
Justin Hunt Posted February 27, 2007 Share Posted February 27, 2007 Have you got the backburner2007 patch? It may help JHV Link to comment Share on other sites More sharing options...
nisus Posted February 28, 2007 Author Share Posted February 28, 2007 64bit, latest bb patch, SP2 nisus Link to comment Share on other sites More sharing options...
nisus Posted March 1, 2007 Author Share Posted March 1, 2007 ok... running the manager on a 32bit machine while the whole network is 64bit is NOT a good idea... (problem solved) nisus Link to comment Share on other sites More sharing options...
Justin Hunt Posted March 1, 2007 Share Posted March 1, 2007 An other one to add to the list of things to watchout in a 32/64 bit environment Glad it sorted JHV Link to comment Share on other sites More sharing options...
dynaman Posted August 2, 2007 Share Posted August 2, 2007 just thought i'd add to this thread...i just experienced the same issue and i'm on a full 32 bit system. i'd be curious if anyone else has been able to resolve this issue. 600 minutes doesn't seem like a very long time these days... Link to comment Share on other sites More sharing options...
ITryMyBest Posted August 2, 2007 Share Posted August 2, 2007 In the BB Monitor, you can right click on the job and go to 'Edit Settings'. Scroll down and you will see 'Timeouts' change 'Wait to Render' from 600 to 2400. This should change the amount of time for one from from 10 hours to 40 hours. You can also click on the 'Advanced' tab at the bottom of the box that comes up after you hit render, and change the 'Wait to Render' value there. Hope this helps Link to comment Share on other sites More sharing options...
dynaman Posted August 2, 2007 Share Posted August 2, 2007 sure - i'll definitely give this a try, but according to earlier postings in this thread it sounds like that doesn't work. waiting 10 hrs to see if it fails is not a very efficient testing system unfortunately... Link to comment Share on other sites More sharing options...
dynaman Posted August 6, 2007 Share Posted August 6, 2007 just thought i'd post back again. i did change the task timeout to 2400 and it seems to have worked as i just got a complete frame that took over 10 hrs. the reason i questioned this is because i had read through a thread on the autodesk site where people had mentioned that even if you change the timeout it would still crap out after 10 hrs. evidently this IS NOT the case, so in fact, manually changing the timeout period appears to work fine. thanks! Link to comment Share on other sites More sharing options...
Jim Lammers Posted March 24, 2008 Share Posted March 24, 2008 "ok... running the manager on a 32bit machine while the whole network is 64bit is NOT a good idea... (problem solved)" Dear Nisus: thanks for posting the solution. We're having the same problem here and I appreciate the tip! Other responders should note that the problem only appears with a 32 bit machine running manager on a farm of 64 bit machines. Jim Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now