My digital ocean droplet have some unecpected shutdowns in the last days.
The droplet ist off and i have to power it on again. If the system requested a power down then a log entry should exist. But there is nothing. Server Logs show normal traffic, nothing special and then boom system off. From my perspective it looks like a Power failure on real hardware without the posibility to capture everything. On a Kernel Panic the system shoud perform a Reboot not a power down. You I try this behavier with sysctl debug.kdb.panic=1
I wrote to the support team but they answer that my guest requested the shutdown and everything is fine with the hypervisor and other systems running on it. So they deny my request to move my droplet to another hypervisor.
At the moment i dont have an idea for future investigation.
System and Services:
- FreeBSD with ZFS
- autossh tunel to another machine
- munin node + master
There is absolutly nothing in my logfiles and "last" dose not show a requested shutdown. Below you will find thelast logline bevor and after from /var/log/messages
I hope you have some Ideas
-> % last | grep shutdown shutdown time Tue Dec 5 09:16 monocult pts/1 xxx Tue Dec 5 09:14 - shutdown (00:02) monocult pts/0 xxx Tue Dec 5 08:36 - shutdown (00:40) shutdown time Sat Dec 2 13:48 monocult pts/0 xxx Sat Dec 2 13:46 - shutdown (00:01) Dec 1 21:39:56 application-server sshd: error: maximum authentication attempts exceeded for invalid user root from xxx port 45166 ssh2 [preauth] Dec 2 13:46:13 application-server syslogd: kernel boot file is /boot/kernel/kernel Dec 5 00:42:33 application-server sshd: error: maximum authentication attempts exceeded for invalid user root from xxx port 52546 ssh2 [preauth] Dec 5 08:34:26 application-server syslogd: kernel boot file is /boot/kernel/kernel