We have been testing Deadline on 2 machines and it seems as though we are having some permissions issues.
The 2 slaves are running OSX 10.6 both connecting to an external XSAN share that has the repository. All permission settings look correct; however, a job submitted from Slave A will be distributed to Slave B but none will render (similar issue to a previous thread http://forums.thinkboxsoftware.com/viewtopic.php?f=11&t=3880&p=15465&hilit=permissions#p15465).
We have tried creating a samba share to the same repository and this works just fine, but our samba share is way too slow to keep this as a solution.
Any hints on how to fix this would be greatly appreciated.
Well, to test if it’s a permission problem, create a text file on one machine, then attempt to edit it from anther using the same login as the slave processes are using. Then reverse the create/edit machines. That should test user permissions.
That said, using the same user account to mount the repository share is the recommended approach. Deadline expects full read/write permissions on the entire repository including newly created files (hence why chmodding everything 777 doesn’t work exactly right). In mixed farms Samba should be used exclusively, but that shouldn’t be necessary here since it’s a 100% OS X environment.
Check the file permissions in the repository. Are there files Deadline isn’t able to read?
Yes, both slave computers are able to read and write to each others created files. The entire repository seems as though they have the correct permissions set. With XSAN Maybe Deadline doesn’t follow the ACL rules specified by XSAN?
Deadline relies on the OS to handle permissions. There’s nothing particularly special there.
Deadline should react similar to the Finder as far as reading and writing files (well, finder doesn’t write, but you know). Do you have a specific user set aside for the Deadline Repository share? We’ve seen issues with per-user ACL configuration for the Deadline share, and tends to be a little messy read/write wise.
The other option which would allow for better ACL would be to create a deadline group, and join users who run Deadline into that group, but you’re creating a lot more work for yourself for virtually the same result.