Noticing an issue when I delete a slave from the Monitor. It shuts down and disappears from the Monitor and from the slave, but when the slave machine is restarted, it reappears. All of our slaves are from a common image so they all exhibit this. Is there a way to permanently delete a slave? Our original image had 2 slave instances per machine and we have abandoned that idea but I cannot get the second slave to delete permanently.
On build 54718 but I have noticed it in all the releases to this point.
In order to stop the second Slave from starting up, you need to first stop the extra Deadline Slaves. Once they’re showing up as offline in the Monitor, instead of just deleting them straight away, you first need to right-click the Slaves you no longer want to start, and select “Remove Slave Instance”, under the Remote Commands menu (this requires Super User permissions by default). This will send a command to the Launcher running on those machines notifying them that they shouldn’t start that Slave instance any more. Once those commands go through, you should be safe to delete the extraneous Slave entries from the Monitor.
I think in the future we might look into automating this step when extra slave instances are deleted – you’re definitely not the first to run into this!
Thanks for pointing me to that but it doesnt seem to have worked. I Disabled the Slave via the Monitor then removed the Slave instance. It disappeared. No worries, life is good.
A couple days later, and for a variety of reasons, I had to restart the primary Slave instance (via the Remote control menu) and the second instance started up again.
Actually, you need to right-click and select Remote Control -> Slave Commands -> Remove Slave Instance. Note that this option will only be available if the slave is in the Offline or Stalled state. You will also be prompted to delete the slave from the repository as well.