Last week I needed to reboot one of our database servers. Unfortunately, that was the one in which Octopus Deploy stores its state and I did not first stop Octopus. After the database server was back on, Octopus showed me this message:
The DRAIN state is normally used to prepare for maintenance activities and lets you tell a node in a cluster that it should stop accepting new work. In our case with only one Octopus node that meant we no longer could deploy our applications.
Luckily for me, DRAIN is a state that we can change in the configuration section. Go to Configuration / Nodes where you can see your machines:
If you click on the three dots at the end of the line a menu opens and let you ‘Disable Node Drain‘:
A few seconds later my machine was back in the state ‘Running‘:
Next time I will stop Octopus Deploy before I reboot the SQL Server. But if that is not possible or someone forgets it, it only takes a push at the right place and everything is back to normal.