The slave in question recently hardlocked and was power cycled. Rebooting and restarting DL 4.1 client in non-GUI mode, no errors have been reported, but the slave has not picked up any work. It’s been idle all day so far (only just noticed) and I’m stumped as to cause. All other nodes are working fine.
DL Monitor just reports the node as idle.
Any ideas?
A couple of things to check:
- Is the slave in the pool & group that your jobs are submitted to (only applicable if you’re not submitting to the ‘none’ pool and group).
- Do you know if this slave had made attempts to render any of your current jobs prior to locking up? If it did, and reported errors during those renders, it may be in the “bad slave list” for those jobs. You can check a job’s bad slave list from it’s right-click menu in the Monitor.
- What happens when you submit a new job? Does it still not participate?
- Finally, check the Volumes folder on the machine (I’m assuming this is a Mac), and see if the repository folder is mounted properly, or if there is a mounted repository with a “-1” appended to the path. If there is, disconnect from the server, clean up any remaining repository folders in /Volumes, and then connect again to see if that helps.
Cheers,
- Yup.
- It isn’t in the bad slave list
- The volume is mounted correctly, and in the correct location.
What I don’t understand is that the slave was listed in the job properties under the blacklisted slave. I didn’t do that myself. 
That would explain why the slave wasn’t picking up the job. Deadline should never change the machine limit settings for a job automatically, and I would normally suggest checking the job’s history log in the Monitor (right-click → Job Reports → View History), but I’ve just discovered that modifying the machine list here doesn’t make into the log. We’ve logged that as a bug.
Cheers,