Cause of stalled Slave

Hi, i wonder what can cause stalled slave,

I got here this morning and had a bunch of my instance stalled.
Can you guide me on what is causing this ?

A slave is considered stalled if it hasn’t updated its state in the Repository in a certain amount of time. The default is 10 minutes, and this can be configured under the Wait Times tab of the Slave Settings in the Repository Options.

Often, there are two main reasons why a slave has stalled:

  1. It crashed or didn’t exit cleanly. In this case, it didn’t have a chance to mark itself as Offline, so after the timeout, it looks like the slave is still running but not updating its state, so it is considered stalled.
  2. The slave is running, but it’s unable to write to its slaveInfo file in the repository because the file is locked or there is a network/permission issue preventing it from doing so. The file it would be writing to is \your\repository\slaves\SLAVENAME\SLAVENAME.slaveInfo. If this was the case, the slave should be complaining about writing to this file in its slave log.

Cheers,

  • Ryan