You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some rooms, particularly Judd113, the shutdown process initiated by shutdown -r now gets through shutting down the ssh daemon, but appears to hang afterwards. Thus the system never reboots. We need to figure out what's hanging up the system in the Linux shutdown process and eliminate it.
The text was updated successfully, but these errors were encountered:
turns out the problem was with RabbitMQ having to spool all the messages to disk every shut down. It would eventually shut down, but only after 10 minutes. Now that rabbitmq restarts every night the queues memory are much smaller when we need to shut down.
However, we still need to fix the problem: rabbitmq should not be taking up so much memory, there should be no persistence, and all messages should be being consumed or flushed by roomtrol.
In some rooms, particularly Judd113, the shutdown process initiated by shutdown -r now gets through shutting down the ssh daemon, but appears to hang afterwards. Thus the system never reboots. We need to figure out what's hanging up the system in the Linux shutdown process and eliminate it.
The text was updated successfully, but these errors were encountered: