linode shuts down unexpectedly
My linode shuts down unexpectedly after 20 min or so. (If the Lassie watchdog is turned on, the linode would self-reboot & re-start every 20 or so).
I have been trying to track the problem by using "journalctl | grep -i shutdown", which contains the following lines:
Oct 31 02:04:17 localhost systemd[1]: Starting Create final runtime dir for shutdown pivot root…
Oct 31 02:04:17 localhost systemd[1]: Finished Create final runtime dir for shutdown pivot root.
Oct 31 02:04:17 localhost systemd[1]: Starting Record System Boot/Shutdown in UTMP…
Oct 31 02:04:17 localhost systemd[1]: Finished Record System Boot/Shutdown in UTMP.
Oct 31 02:04:25 localhost systemd[1]: Started Unattended Upgrades Shutdown.
I then turned off the auto-upgrade in the following file "/etc/apt/apt.conf.d/20auto-upgrades" by setting both values to 0.
Problem persists. Please help!
2 Replies
mjones
Linode Staff
Hi @qiulab - The best place to start looking for a problem is in your system logs. There's another post with info on how to check them:
https://www.linode.com/community/questions/295/how-do-i-check-my-servers-log-files
Other than that, you may want to double check to see if your Linode's disk is nearly completely full, and is filling up with temporary files while running. You can check with:
df -h
df -ih
The first will check disk usage and the second will check inodes.
Hi, mjones,
Thanks for your reply. Disk space could be an issue. Please let me know if you see any problem with the following outputs:
df -ih
Filesystem Inodes IUsed IFree IUse% Mounted on
tmpfs 491K 785 490K 1% /run
/dev/sda 4.9M 281K 4.6M 6% /
tmpfs 491K 3 491K 1% /dev/shm
tmpfs 491K 4 491K 1% /run/lock
tmpfs 99K 58 99K 1% /run/user/124
tmpfs 99K 48 99K 1% /run/user/1001
df -h:
Filesystem Size Used Avail Use% Mounted on
tmpfs 393M 1.3M 392M 1% /run
/dev/sda 79G 60G 15G 80% /
tmpfs 2.0G 44K 2.0G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 393M 44K 393M 1% /run/user/124
tmpfs 393M 32K 393M 1% /run/user/1001
I couldn't quite decipher the system log files (other than running "journalctl | grep -i shutdown", which a staff assured me that unattended upgrade is not the problem).
I unmounted the newly attached volume, but the problem persists. I'm now left with the option of running rescue or rebuilding the node (with the risk of losing all data).
any other advice would be greatly appreciated!
Weigang