如何确定系统崩溃的原因？

Question

如何确定系统崩溃的原因？

20

我的服务器大约每周崩溃一次，而且没有任何线索表明是什么原因导致的。我已经检查了/var/log/messages文件，但它在某个时间点停止记录，并在我执行硬重启时开始记录计算机的后台信息。有没有什么我可以检查或安装的软件来确定原因？我正在运行CentOS 7。这是我/var/log/dmesg文件中唯一的错误/问题：https://paste.netcoding.net/cosisiloji.log

[    3.606936] md: Waiting for all devices to be available before autodetect
[    3.606984] md: If you don't use raid, use raid=noautodetect
[    3.607085] md: Autodetecting RAID arrays.
[    3.608309] md: Scanned 6 and added 6 devices.
[    3.608362] md: autorun ...
[    3.608412] md: considering sdc2 ...
[    3.608464] md:  adding sdc2 ...
[    3.608516] md: sdc1 has different UUID to sdc2
[    3.608570] md:  adding sdb2 ...
[    3.608620] md: sdb1 has different UUID to sdc2
[    3.608674] md:  adding sda2 ...
[    3.608726] md: sda1 has different UUID to sdc2
[    3.608944] md: created md2
[    3.608997] md: bind<sda2>
[    3.609058] md: bind<sdb2>
[    3.609116] md: bind<sdc2>
[    3.609175] md: running: <sdc2><sdb2><sda2>
[    3.609548] md/raid1:md2: active with 3 out of 3 mirrors
[    3.609623] md2: detected capacity change from 0 to 98520989696
[    3.609685] md: considering sdc1 ...
[    3.609737] md:  adding sdc1 ...
[    3.609789] md:  adding sdb1 ...
[    3.609841] md:  adding sda1 ...
[    3.610005] md: created md1
[    3.610055] md: bind<sda1>
[    3.610117] md: bind<sdb1>
[    3.610175] md: bind<sdc1>
[    3.610233] md: running: <sdc1><sdb1><sda1>
[    3.610714] md/raid1:md1: not clean -- starting background reconstruction
[    3.610773] md/raid1:md1: active with 3 out of 3 mirrors
[    3.610854] md1: detected capacity change from 0 to 20970405888
[    3.610917] md: ... autorun DONE.
[    3.610999] md: resync of RAID array md1
[    3.611054] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[    3.611119] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.
[    3.611180] md: using 128k window, over a total of 20478912k.
[    3.611244]  md1: unknown partition table
[    3.624786] EXT3-fs (md1): error: couldn't mount because of unsupported optional features (240)
[    3.627095] EXT2-fs (md1): error: couldn't mount because of unsupported optional features (244)
[    3.630284] EXT4-fs (md1): INFO: recovery required on readonly filesystem
[    3.630341] EXT4-fs (md1): write access will be enabled during recovery
[    3.819411] EXT4-fs (md1): orphan cleanup on readonly fs
[    3.836922] EXT4-fs (md1): 24 orphan inodes deleted
[    3.836975] EXT4-fs (md1): recovery complete
[    3.840557] EXT4-fs (md1): mounted filesystem with ordered data mode. Opts: (null)

- Nahydrin

3个回答

6

你可以在/var/log/dmesg中查看dmesg文件，该文件记录了内核消息。消息日志只记录服务和应用程序的消息，如果出现内核错误，服务和应用程序将停止运行，但内核错误仍会被记录在dmesg中。

- TooCloudy

我查看了 dmesg 和 dmesg.old，两者都只包含启动信息（大约4.8秒）。我能看到的唯一"问题"是启动磁盘或RAID驱动器似乎有一些问题，但系统会修复它并正常工作。请查看主贴获取链接。 - Nahydrin

3

BIOS内存测试
BIOS硬盘测试
检查智能驱动器日志 smartctl /dev/sda -a
智能驱动器测试
在一个窗口中保持dmesg -wH运行

- Jim U

我已经对这三个驱动器进行了智能驱动器测试，它们没有损坏。我在一个窗口中运行着 dmesg -wH 命令（我假设直到它再次崩溃；并且在通过 SSH 读取崩溃后的输出）。我无法物理接触这台机器，所以我应该要求我的主机运行 BIOS 内存和硬盘测试吗？ - Nahydrin

- shodanshok · Accepted Answer

如果您已经安装并启用了crashkernel/kdump，您应该能够使用crash实用程序相对容易地检查崩溃的内核。例如，假设您的崩溃内核转储保存在/var/crash下：crash /var/crash/2009-07-17-10\:36/vmcore /usr/lib/debug/lib/modules/uname -r/vmlinux。有关更多详细信息，请查看这里和这里。