Hi Everyone!
I’m new to the forum. So one of the slaves I use got stalled. At that time it couldn’t connect to the Repository anymore either. After looking on the internet to unstall it I right clicked on the slave in the Deadline Monitor and set it on ‘Mark slave as offline’. in the hope after a total system reboot it would get picked up again. But it didn’t. How do I get the slave to connect to the Repository and have it working again?
Please let me know and thanks in advance.
Kind regards.
The Slave status display in the Monitor is based mainly on communication from the Slave to the Deadline database. The Slave periodically writes timestamps and status info (e.g. Rendering, Idle etc.) to the DB. If it fails to report back for a significant period of time, it gets marked as Stalled. At that point, setting its status to Offline is a manual write operation on the DB, but does not affect the actual Slave application on the render node. If the Slave were online, it would update its status in the Monitor to Online as soon as it writes into the DB.
In other words, the only way to “revive” a Slave is to restart the Slave application on the render node. Restarting the render node could help, esp. if the Slave application was set up to autostart on Deadline Launcher startup.
Typically the reason for the stalled state is that either the Slave cannot communicate with the Repository, or the Slave application has crashed. You should log into that machine and try to find and solve the problem there. The Monitor is just a dashboard reflecting the content of the database. It has some remote management tools, but if the problem is in the network communication, they are unlikely to help.