My server underwent an unannounced reboot today, Dec 30, at 10:17 AM (SGT), causing significant downtime for my application. This is unacceptable for a service I rely on, especially as I have already launched my service.
I have analyzed the system logs to confirm this was a clean, initiated shutdown and not a crash. Here are the facts from my journalctl and last reboot logs: Event: System received a formal shutdown/power-off signal at 10:17:19.
Log Proof: The journal shows systemd-poweroff.service was activated, and the system reached target System Power Off gracefully. Downtime: The system was back up by 10:17:42, confirming a rapid restart. Impact: My Python process (birthplaceapp.py), which was running via nohup, was terminated during the SIGTERM phase of the shutdown.
My Questions: Why was there no advance notice or email regarding this maintenance/reboot? Was this triggered by a platform-wide update, and how can I ensure I am notified of these events in the future to prevent service interruptions? I expect a stable environment for my deployments. Please look into this instance and provide an explanation for the lack of communication.
Serve ID - server-693f965eceef79f31e982731