質問: ubuntuサーバーが再起動した理由を調べるにはどうすればよいですか? vpsが再起動したという警告をvpsホストから受け取りました。/var/logs/auth.logには、次のエントリが表示されます。 mar 17 19:09:34 master sshd[3558]: server listening on 0.0.0.0 port 9922. mar 17 19:09:34 master sshd[3558]: server listening on :: port 9922. mar 17 19:09:34 master systemd-logind[3539]: watching system buttons on /dev/input/event0 (power button) mar 17 19:09:34 master systemd-logind[3539]: new seat seat0. テキストエディタでファイルを開くと、最初の行の前のスペースはすべてnulsです。/var/log/syslogには、次が表示されます。mar 17 19:09:34 master rsyslogd: [origin software="rsyslogd" swversion="7.4.4" x-pid="3518" x-info="http://www.rsyslog.com"] start mar 17 19:09:34 master rsyslogd: rsyslogd's groupid changed to 109 mar 17 19:09:34 master rsyslogd: rsyslogd's userid changed to 104 mar 17 19:09:34 master systemd-udevd[3079]: starting version 219 mar 17 19:09:34 master ufw-init[2040]: modprobe: error: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.7-x86_64-linode80/modules.dep.bin' mar 17 19:09:34 master networking[3095]: * configuring network interfaces... mar 17 19:09:34 master systemd[1]: started udev kernel device manager. mar 17 19:09:34 master systemd[1]: started show plymouth boot screen. mar 17 19:09:34 master systemd[1]: started dispatch password requests to console directory watch. mar 17 19:09:34 master systemd[1]: starting dispatch password requests to console directory watch. mar 17 19:09:34 master systemd[1]: reached target paths. mar 17 19:09:34 master systemd[1]: starting paths. mar 17 19:09:34 master systemd[1]: started forward password requests to plymouth directory watch. mar 17 19:09:34 master systemd[1]: starting copy rules generated while the root was ro... mar 17 19:09:34 master systemd[1]: starting flush journal to persistent storage... mar 17 19:09:34 master systemd[1]: found device /dev/ttys0. mar 17 19:09:34 master systemd[1]: started copy rules generated while the root was ro. mar 17 19:09:34 master systemd[1]: started flush journal to persistent storage. mar 17 19:09:34 master systemd[1]: starting create volatile files and directories... mar 17 19:09:34 master loadkeys[3082]: loading /etc/console-setup/cached.kmap.gz mar 17 19:09:34 master systemd-tmpfiles[3159]: [/usr/lib/tmpfiles.d/var.conf:14] duplicate line for path "/var/log", ignoring. mar 17 19:09:34 master systemd[1]: started set console keymap. mar 17 19:09:34 master systemd-udevd[3123]: could not open moddep file '/lib/modules/4.9.7-x86_64-linode80/modules.dep.bin' mar 17 19:09:34 master systemd-udevd[3122]: could not open moddep file '/lib/modules/4.9.7-x86_64-linode80/modules.dep.bin' mar 17 19:09:34 master systemd-udevd[3121]: could not open moddep file '/lib/modules/4.9.7-x86_64-linode80/modules.dep.bin' mar 17 19:09:34 master systemd[1]: started create volatile files and directories. mar 17 19:09:34 master systemd[1]: started network time synchronization. mar 17 19:09:34 master systemd[1]: reached target system time synchronized. mar 17 19:09:34 master systemd[1]: starting system time synchronized. mar 17 19:09:34 master systemd[1]: starting update utmp about system boot/shutdown... mar 17 19:09:34 master systemd-udevd[3127]: could not generate persistent mac address for dummy0: no such file or directory mar 17 19:09:34 master systemd-udevd[3124]: could not generate persistent mac address for ip6tnl0: no such file or directory mar 17 19:09:34 master systemd[1]: started update utmp about system boot/shutdown. mar 17 19:09:34 master systemd[1]: found device qemu_harddisk. mar 17 19:09:34 master systemd[1]: started uncomplicated firewall. mar 17 19:09:34 master systemd[1]: activating swap /dev/sdb... mar 17 19:09:34 master systemd[1]: created slice system-ifup.slice. ... 再起動の原因は何ですか?
回答: 私はプロバイダーに話を聞いたところ、vpsがホストされているハイパーバイザーに問題があることを確認したため、マシンを再起動する必要がありました。