Hi,
I’ve been trying to setup my render farm on Centos 6. We have Linux machines working on Nuke, they have deadline installed they get to submit to the farm and all that is fine. But when a Linux slave on the farm takes a job, sometimes it works - although most of the time it grabs all of the job’s frames, and doesn’t render anything, just crashes.
I have noticed that Deadline 5 and up have improved stability under linux, although for now upgrading everything to deadline 5 is not an option. Is this a known issue for Deadline 4?
This sounds like a known issue when there are permission problems with the repository (the issue was discovered in Deadline 5.0, so it more than likely is an issue with Deadline 4). If you have the chance to upgrade, I would skip Deadline 5 and move right to 6, as this type of permission issue is no longer a factor because we store this information in a database. The Deadline applications have a native user interface in Deadline 6 as well, making the Linux experience much more enjoyable.
I would double check permissions on the Repository to make sure they’re completely open. Basically, everyone needs to be able to create, modify, and delete all files and folders. This documentation might help, even though it’s for Deadline 6:
thinkboxsoftware.com/deadlin … epo/#Linux
Cheers,
Thanks for the quick reply. The permissions are fine with the repository. So I guess my only option is to upgrade to deadline 6. Is a deadline 5/6 slave able to render on a Deadline 4 Repository?
If not, then I guess our linux’s will have to wait!
No, you’ll need to install a fresh repository. This is a typical requirement for any major upgrade. Since over half the data is stored in a database for Deadline 6, it flat out wouldn’t work with a v4 repository. 
If you have a support an upgrade contract, maybe you could get your license upgraded to Deadline 6, and then run version 6 on your Linux slaves. That would mean having two separate repositories, but that might help speed up your transition to v6.
Cheers,