Backburner Renders Timing out - but this is disabled!

[OrionD]

did anything change in ur workstation, manager machine or thes servers, eg. windows update, backburner update or permissions change, or a new user account added. could be a lot of variable that could screw up the windows accounts. seems like a permissions issue as it's not updating those numbers in the xml file even after u send the settings with the render.

try another thing - send a job as "initialy suspended". then in the monitor, change the settings and now start the job. see if this works.

or try starting the manager on a different machine for a change/test...

hope this helps...

[rhino]

I remember reading the upper wait to render limit is 40000, maybe 70000 is invalid. I have mine set to 40000 with no problems

[emptyvoxel]

We had this problem as well, and simply rolled back to Backburner Manager 2.3.
You can still continue to use Queue Monitor and Server v3.0, but as long as the job is submitted to a 2.3 manager, in my experience, it will respect the custom timeouts.

[sv]

did anything change in ur workstation, manager machine or thes servers, eg. windows update, backburner update or permissions change, or a new user account added. could be a lot of variable that could screw up the windows accounts. seems like a permissions issue as it's not updating those numbers in the xml file even after u send the settings with the render.

i didn't change anything, but it's possible someone has changed something on the network without knowing the consequences. Just got to get on with it now...
I've installed 3.0.2, but it's so late in the day i'll have to try other methods, like sitting with my pc over the weekend and using DR....

I remember reading the upper wait to render limit is 40000, maybe 70000 is invalid. I have mine set to 40000 with no problems

Yes i think the amounts have changed, but in version 3.0.2 at least 70000 will be accepted as the highest possible input. i'm sure that 40000 would suffise though, so i might change to this....

We had this problem as well, and simply rolled back to Backburner Manager 2.3.

I remember when i installed v.3 and i thought it was a complete sack of crap, 2.3 worked flawlessly (in my experience) for years, i've no idea why you would fix something that isn't broke.


EDIT: I'll try this if all else fails, because i'd rather not downgrade 20 or so machines, just takes a while....

EDIT: Sorry, i've just read your post properly, i'd only need to change the one manager... hmm, might try this then... thanks for the advice....






thanks for all your help. I'll be glad to see the back of this job......

[zoranm]

Do you have max installed on the Manager's machine?

600min limit might be due to this

Z.

[sv]

Thought i should report back to anyone who may come accross this thread in the future, that, as marco pointed out, the 3.0.2 update does fix the timeout bug, even though this isn't reported as a bug fix....

The renders have finally finished today, with the 3.0.2 update saving the day.

Thanks for all inputs, and hopefully BB 2007 can sort somethings out.......

ta.

[marco]

nice !

the 3.0.2 update does fix the timeout bug, even though this isn't reported as a bug fix....

probably autodesk isn't even aware of this bug.
I'm afraid BB2007 will have other issues, they probably spend months on renaming it, instead of bugfixing it......

Marco

[armilla]

Hi,
Did anyone ever find a definitive answer to this issue? There seems to be some conflicting information in this post - "sv" resolved the problem by installing BB 3.0.2, whilst "marco" was still having trouble with BB 3.0.2. Installing max on the manager works for some people and not others.

We're on 3.0.2 and have not managed to find a way round it, despite numerous searches on this and the Autodesk forum. Pleeeease can anyone help?

Many thanks.

[marco]

Hi,
Did anyone ever find a definitive answer to this issue? There seems to be some conflicting information in this post - "sv" resolved the problem by installing BB 3.0.2, whilst "marco" was still having trouble with BB 3.0.2. Installing max on the manager works for some people and not others.

We're on 3.0.2 and have not managed to find a way round it, despite numerous searches on this and the Autodesk forum. Pleeeease can anyone help?

Many thanks.

please read my last post carefully...., it says"now that I installed 3.02 it seems that backburner doesn't overrule the rendertimeout to 600 min anymore ! "
No problems with 3.02 anymore, just like SV

did you edit backburner.xml on the workstation submitting the jobs like this ?
<UseTimeouts>YES</UseTimeouts>
<MaxLoad>30</MaxLoad>
<MaxUnload>10</MaxUnload>
<MaxRender>6000</MaxRender>

Marco

[sv]

yeah, the 3.0.2 fix solved the problem for me, although it's not mentioned as a bug fix.

[armilla]

Thanks for the fast reply guys - it's much appreciated. Apologies for mis-reading your reply Marco, but believe me I've been round and round in circles trying to sort this out. Anyway, I've checked the backburner.xml file on the workstation I submitted the jobs from, and the lines of text that you show are not there, which is odd. I've checked one of the other workstations though, and it's the same as in your post, so the plan is to try and submit the jobs from that machine tonight and hope for the best. I'll let you know how it goes in the morning. Thanks again.

[Dman3d]

I just got fried by BB2007 lasy night. Three highres all restared, looking into the sp2 for it but no time at present, resorting to DR but probably wont make it.

[dbuchhofer]

I'll confess i didn't read the thread, but one instance where Backburner will timeout irregardless of what you have the values set to is when the manager doesn't have max installed on it, or when the manager machine has a different (read: older) version of max installed.

[armilla]

Sorry about the delay in getting back with an answer, but it was only yesterday that I had the opportunity to install max on the manager, and hey presto I'm now able to render images that were previously timing out at 10 hours. Many thanks to everyone for their help.