Tweet
I have DR running well on our renderfarm now, but I am now trying to configure backburner on our farm. It has been working flawlessly for years, but we have recently built new workstations (from where the jobs are sent) and since then, backburner on our original set of render slaves fails to run properly (3 newer machines however work just fine).
All render slaves have backburner running as a service with the same login admin credentials as the vray spawner service (which works fine). In this setup, only our 3 newest render slaves actually render the frames from a backburner job. Our original 8 render slaves are reported to be busy, but when you remote desktop into them, they are doing nothing (no CPU activity etc). They eventually timeout.
If, however, we remove backburner as a service and instead run it normally, the jobs pickup just fine.
Its very weird as bb used to run just fine on these machines. Its only since having new workstations that the problem seems to have surfaced.
Any tips on what to check?
All render slaves have backburner running as a service with the same login admin credentials as the vray spawner service (which works fine). In this setup, only our 3 newest render slaves actually render the frames from a backburner job. Our original 8 render slaves are reported to be busy, but when you remote desktop into them, they are doing nothing (no CPU activity etc). They eventually timeout.
If, however, we remove backburner as a service and instead run it normally, the jobs pickup just fine.
Its very weird as bb used to run just fine on these machines. Its only since having new workstations that the problem seems to have surfaced.
Any tips on what to check?
