LAN 깨우기 직후에 컴퓨터가 멈춥니다. 그렇지 않으면 정상적으로 작동합니다.

LAN 깨우기 직후에 컴퓨터가 멈춥니다. 그렇지 않으면 정상적으로 작동합니다.

저 멀리 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(아마도) 자체로는 충분히 도움이 되지 않습니다.

관련 정보