after upgrading to backburner 3, it appears that the rendermanager is overruling the per-job-timeout-settings from a submitted renderjob.
-I already modified the backburner.xml file on both workstation and dedicated rendermanager system to: (this worked fine in previous backburner shipped with max6)
<UseTimeouts>Yes
<MaxLoad>20
<MaxUnload>10
<MaxRender>1200
-after submitting a job and then checking “job settings” in the queue monitor it correctly states :
timeouts:
wait to load:20
wait to unload:10
wait to render:1200
BUT when rendering this very job, the rendering is aborted after 10 hours (600 min) with the following task error: task timeout (600 minutes) !!! :shock:
changing the rendertimeout in the job settings of queuemonitor to for instance 3 minutes results in a rendertimeout after 3 minutes, which is correct…
It appears that the rendermanager is overruling the job timeout-settings in the queuemonitor
how is this possible ???
as you can imagine there are plenty of renderjobs that require more then 10 hours to render, which now is impossible !
is there a way to bypass this 600 min timeout overrule, and raise this default timeout to another value ?
I read that post before I posted, they are talking about backburner 2.
I modified the backburner.xml with backburner2 just like that, and everything worked fine for 2 years.
but after upgrading to max8 sp3 and backburner 3 it doen’t work anymore…
there must be more people having this problem I guess.
I’m in the same boat. When I launch the backburner manager, it overwrites my backburner.xml file with a new one that doesn’t include those timeout values. It also ignores the per-job timeout settings when submitting a job.
There’s got to be a way to fix this. I’m tired of compositing stills just to keep my renders under 10 hours.
If you right click the job in backburner manager and click edit settings you can change the timeout settings. Does this make a difference or do these settings get ignored as well?
If you right click the job in backburner manager and click edit settings you can change the timeout settings. Does this make a difference or do these settings get ignored as well?
No, these settings are not ignored, the problem is that they get overruled if they are higher than 600 minutes.
(for example a rendertimeout setting of 10 min will work fine, 1500 minutes gets overruled after 10 hours …)
we had similar problems, even though we changed the config file. It turned out that the manager machine had to have max installed. Where we only installed bb 3 on it. After that, we were able to render frames for 25 hours per frame.
I guess you’ll have to give them at least 2x10 hour+ to respond to your question
I’d prefer the timout to be optional. If I want to use it for a sequence I would probably still optimize the settings. 10 hours is a bit long for a timout if I make a animation and don’t want my servers to get stuck.
So I sometimes don’t do a calulation as to how long it’s going to take to finnish. I know it will be fine. Just let it render. And how many timouts did I have last week? i don’t know but it was more than I wanted.
we had similar problems, even though we changed the config file. It turned out that the manager machine had to have max installed. Where we only installed bb 3 on it. After that, we were able to render frames for 25 hours per frame.
Morbid, thats what I understood from another forum post at the autodesk forum.
the problem is that my manager machine also is a rendernode which means it already has a full 3dsmax install…
it really pisses me off that autodesk was thinking “hmm, as an update for backburner lets overrule custom timeout setting above 10 hours to 10 hours because such long frame times are not realistic anymore…”
Autodesk should leave this choice to their customers, and not make that decision beforehand in their software. :twisted:
Maybe with max9 we’ll get a newer version of backburner with a fix for this bug (and consequently there will probably will be other things that don’t work anymore…)
I guess you’ll have to give them at least 2x10 hour+ to respond to your question
no probably 10 years, that forum is slowwwww…
we regularly render rediculous renders, well over 10 hours and have not had the problem. Most of the slaves are running SP3 with BB 3.02 but we still use 2.3 monitor since the 3.01 and 3.02 did not seem to fix the monitor
crash problem that plagues us.
Nothing special going on but override when sending the render to
rediclous settings like 7000, 20000, 7000 for time
running VRay 1.47.03
My problem is that I don’t reset the timeout every time. And Why should I have to? It’s optional to use “all servers” althogh it’s quite useful when rendering a animation. I can see the use of timout but really. This does not streamline my workflow. It’s extra work for every rendering. Thank you very much. At least give me the option to set it once to something like a year and be done with it.
OK, although autodesk doesn’t mention any fixes in backburner 3.02 related to the issue discussed in this thread, I’ll install the 3.02 one the manager and one rendernode and see if it is OK.
I’ll report back with the results…
Ummm… yeah… this happened to me again last night. I think we should get a group together, find the person who messed up backburner, and punch them squarely in the nose.
It seems that when you set your task timeout to 1200 minutes, it shouldn’t timeout after 600 minutes. Maybe?
When you submit the job, do you click the Advanced button, Enable the time-out override and set it to 70000 (=max?)
I have no idea what the XML option is and what it does. We do have renders that take over 10 hours but I always use the option I mentioned before.
