We have started noticing more and more that restarting the octoprint server will prevent it from completely shutting down. We have found that some plugins can block the Shutdown Plugin from firing after receiving the termination signal from linux. When those plugins are disabled, the shutdown plugin works fine.
What should we do about it?
Find out if there is a way to shore up the signal termination code. Right now it looks like octoprint it using the standard package signal to capture the termination signal. Which is a very standard way of capturing the termination signal. Find out what is blocking the termination code from firing and fix it.
What is this bug?
We have started noticing more and more that restarting the octoprint server will prevent it from completely shutting down. We have found that some plugins can block the Shutdown Plugin from firing after receiving the termination signal from linux. When those plugins are disabled, the shutdown plugin works fine.
What should we do about it?
Find out if there is a way to shore up the signal termination code. Right now it looks like octoprint it using the standard package signal to capture the termination signal. Which is a very standard way of capturing the termination signal. Find out what is blocking the termination code from firing and fix it.