![网络唤醒后不久机器就挂起,否则工作正常](https://linux22.com/image/204918/%E7%BD%91%E7%BB%9C%E5%94%A4%E9%86%92%E5%90%8E%E4%B8%8D%E4%B9%85%E6%9C%BA%E5%99%A8%E5%B0%B1%E6%8C%82%E8%B5%B7%EF%BC%8C%E5%90%A6%E5%88%99%E5%B7%A5%E4%BD%9C%E6%AD%A3%E5%B8%B8.png)
我在很远的地方有一台 Debian Linux 机器。当我使用 WOL 打开它时,它启动正常并工作大约 15 分钟,然后在网络上变得无法访问。当我走到那里时,我仍然可以从控制台登录,这很不方便。
当我关闭它、重新启动并从控制台登录时,一切都很好。然后它会无限期地保持下去。
我知道 这个答案这似乎是相关的。但是当我发出
arp -s 158.227.90.30 00:15:17:41:00:40
根据建议,我得到:
SIOCSARP: Argumento inválido
下面是系统日志最后几行的摘录,我无法完全解释。我不知道还能尝试什么。
Apr 20 09:31:17 B012526 vmunix: [ 1231.510751] PM: suspend entry (s2idle)
Apr 20 09:31:17 B012526 vmunix: [ 1231.510754] PM: Syncing filesystems ... done.
Apr 20 09:45:22 B012526 vmunix: [ 1231.739150] Freezing user space processes ... (elapsed 0.001 seconds) done.
Apr 20 09:45:22 B012526 vmunix: [ 1231.740905] OOM killer disabled.
Apr 20 09:45:22 B012526 vmunix: [ 1231.740906] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Apr 20 09:45:22 B012526 vmunix: [ 1231.742181] Suspending console(s) (use no_console_suspend to debug)
Apr 20 09:45:22 B012526 vmunix: [ 1231.764857] sd 3:0:4:0: [sde] Synchronizing SCSI cache
Apr 20 09:45:22 B012526 vmunix: [ 1231.784851] sd 3:0:3:0: [sdd] Synchronizing SCSI cache
Apr 20 09:45:22 B012526 vmunix: [ 1231.800826] sd 3:0:2:0: [sdc] Synchronizing SCSI cache
Apr 20 09:45:22 B012526 vmunix: [ 1231.816826] sd 3:0:1:0: [sdb] Synchronizing SCSI cache
Apr 20 09:45:22 B012526 vmunix: [ 1231.832827] sd 3:0:0:0: [sda] Synchronizing SCSI cache
Apr 20 09:45:22 B012526 vmunix: [ 1231.837227] serial 00:06: disabled
Apr 20 09:45:22 B012526 vmunix: [ 1231.837273] serial 00:05: disabled
Apr 20 09:45:22 B012526 vmunix: [ 1231.837354] e1000e: EEE TX LPI TIMER: 00000000
Apr 20 09:45:22 B012526 vmunix: [ 1231.837374] e1000e: EEE TX LPI TIMER: 00000000
Apr 20 09:45:22 B012526 vmunix: [ 1231.837396] mptbase: ioc0: pci-suspend: pdev=0x00000000521aadd5, slot=0000:04:00.0, Entering operating state [D3]
Apr 20 09:45:22 B012526 vmunix: [ 1232.180822] radeon 0000:0d:0c.0: Refused to change power state, currently in D0
Apr 20 07:45:22 B012526 rtkit-daemon[1095]: The canary thread is apparently starving. Taking action.
Apr 20 09:45:22 B012526 vmunix: [ 1232.473794] usb usb4: root hub lost power or was reset
Apr 20 09:45:22 B012526 vmunix: [ 1232.473825] lpc_ich 0000:00:1f.0: rerouting interrupts for [8086:2670]
Apr 20 09:45:22 B012526 vmunix: [ 1232.473885] mptbase: ioc0: pci-resume: pdev=0x00000000521aadd5, slot=0000:04:00.0, Previous operating state [D0]
Apr 20 09:45:22 B012526 vmunix: [ 1232.473938] usb usb2: root hub lost power or was reset
Apr 20 09:45:22 B012526 vmunix: [ 1232.474164] mptbase: ioc0: pci-resume: ioc-state=0x1,doorbell=0x10000000
Apr 20 09:45:22 B012526 vmunix: [ 1232.474273] serial 00:05: activated
Apr 20 09:45:22 B012526 vmunix: [ 1232.474285] usb usb3: root hub lost power or was reset
Apr 20 09:45:22 B012526 vmunix: [ 1232.474293] usb usb5: root hub lost power or was reset
Apr 20 09:45:22 B012526 vmunix: [ 1232.475156] ata1.00: unexpected _GTF length (8)
Apr 20 09:45:22 B012526 vmunix: [ 1232.475189] serial 00:06: activated
Apr 20 09:45:22 B012526 vmunix: [ 1232.482418] e1000e 0000:05:00.0 enp5s0f0: MAC Wakeup cause - Magic Packet
Apr 20 09:45:22 B012526 vmunix: [ 1232.852724] [drm] PCI GART of 512M enabled (table at 0x0000000034900000).
Apr 20 09:45:22 B012526 vmunix: [ 1232.852728] radeon 0000:0d:0c.0: WB disabled
Apr 20 09:45:22 B012526 vmunix: [ 1232.852732] radeon 0000:0d:0c.0: fence driver on ring 0 use gpu addr 0x0000000090000000 and cpu addr 0x00000000349b3527
Apr 20 07:45:22 B012526 rtkit-daemon[1095]: Demoting known real-time threads.
Apr 20 09:45:22 B012526 vmunix: [ 1232.852832] [drm] radeon: ring at 0x0000000090001000
Apr 20 09:45:22 B012526 vmunix: [ 1232.852891] [drm] ring test succeeded in 1 usecs
Apr 20 09:45:22 B012526 vmunix: [ 1232.852944] [drm] ib test succeeded in 0 usecs
Apr 20 09:45:22 B012526 vmunix: [ 1232.892920] usb 2-1: reset low-speed USB device number 2 using uhci_hcd
Apr 20 09:45:22 B012526 vmunix: [ 1235.644819] mptbase: ioc0: Sending mpt_do_ioc_recovery
Apr 20 09:45:22 B012526 vmunix: [ 1235.644821] mptbase: ioc0: Initiating bringup
Apr 20 09:45:22 B012526 vmunix: [ 1235.668248] e1000e: enp5s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Apr 20 09:45:22 B012526 vmunix: [ 1236.484810] ioc0: LSISAS1064E B2: Capabilities={Initiator}
Apr 20 09:45:22 B012526 vmunix: [ 1246.398765] mptbase: ioc0: pci-resume: success
Apr 20 09:45:22 B012526 vmunix: [ 1246.399467] OOM killer enabled.
Apr 20 09:45:22 B012526 vmunix: [ 1246.399468] Restarting tasks ... done.
Apr 20 09:45:22 B012526 vmunix: [ 1246.401054] PM: suspend exit
Apr 20 07:45:22 B012526 rtkit-daemon[1095]: Successfully demoted thread 1094 of process 1094 (n/a).
Apr 20 07:45:22 B012526 rtkit-daemon[1095]: Demoted 1 threads.
Apr 20 09:45:31 B012526 vmunix: [ 1255.730216] perf: interrupt took too long (3143 > 3138), lowering kernel.perf_event_max_sample_rate to 63500
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.A11ySettings.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Datetime.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Housekeeping.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Mouse.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.PrintNotifications.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.ScreensaverProxy.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Smartcard.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Rfkill.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Clipboard.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.Sound.desktop' killed by signal 15
Apr 20 09:45:36 B012526 gnome-session-binary[1029]: WARNING: Application 'org.gnome.SettingsDaemon.XSettings.desktop' killed by signal 15
答案1
Apr 20 09:45:22 B012526 vmunix: [ 1246.399467] OOM killer enabled.
不好了 :(
OOM 杀手是内核的一部分,当系统内存严重不足时,它会唤醒并开始杀死进程。我猜 OOM 杀手决定杀死 SSH 守护进程,这就是你被踢的原因。
重新启动它并监视内存使用情况,直到找出是什么耗尽了所有内存,然后报告回来。 Dmesg(可能)本身并没有足够的帮助。