ubuntu系统卡住原因分析

Question

有若干台ubuntu14.04服务器，无法ping通，接上键盘和鼠标依然无法操作，只好重启，结果syslog中有如下日志，从这些日志中能看出什么吗？

从zabbix监控来看，是这条日志后，监控获取不到数据了，'org.freedesktop.systemd1'

Feb 12 09:15:01 node4 CRON[9349]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 12 09:17:01 node4 CRON[9481]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 12 09:31:07 node4 dbus[1349]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper)
Feb 12 09:31:07 node4 dbus[1349]: [system] Successfully activated service 'org.freedesktop.systemd1'
Feb 12 09:31:07 node4 kernel: [12699509.734365] init: tty4 main process (1445) killed by TERM signal
Feb 12 09:31:07 node4 kernel: [12699509.734760] init: tty5 main process (1448) killed by TERM signal
Feb 12 09:31:07 node4 kernel: [12699509.735110] init: tty2 main process (1453) killed by TERM signal
Feb 12 09:31:07 node4 kernel: [12699509.735446] init: tty3 main process (1454) killed by TERM signal
Feb 12 09:31:07 node4 kernel: [12699509.735808] init: tty6 main process (1456) killed by TERM signal
Feb 12 09:31:07 node4 kernel: [12699509.736475] init: cron main process (1486) killed by TERM signal
Feb 12 09:31:07 node4 kernel: [12699509.736806] init: irqbalance main process (1524) killed by TERM signal
Feb 12 09:31:07 node4 kernel: [12699509.737161] init: tty1 main process (1603) killed by TERM signal
Feb 12 06:45:37 node4 rsyslogd: message repeated 169 times: [ [origin software="rsyslogd" swVersion="7.4.4" x-pid="1485" x-info="http://www.rsyslog.com"] rsyslogd was HUPed]
Feb 12 09:31:07 node4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="1485" x-info="http://www.rsyslog.com"] exiting on signal 15.
Feb 12 09:33:50 node4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="1265" x-info="http://www.rsyslog.com"] start
Feb 12 09:33:50 node4 rsyslogd: rsyslogd's groupid changed to 104
Feb 12 09:33:50 node4 rsyslogd: rsyslogd's userid changed to 101
Feb 12 09:33:50 node4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Feb 12 09:33:50 node4 kernel: [    0.000000] Initializing cgroup subsys cpu

Answer 1

闹剧一场，上面的内容是主动重启服务器时的日志记录。节点1挂了，客户搞错了去重启节点2才出现了上面的日志。沉痛的教训，忙活大半天。