Proxmox 서버에 문제가 있습니다. 때때로 내 서버에 액세스할 수 없습니다. Ping 또는 Ssh가 작동하지 않습니다. 무슨 일이 일어나는지 확인하기 위해 화면을 서버에 연결하려고 했지만 이미지가 없습니다. 서버가 켜져 있습니다. 팬이 돌아가는 소리가 들립니다.
저는 proxmox(KVM)를 사용하고 있습니다. 로그를 확인했지만 오전 6시 25분부터 오후 12시 50분 사이에 로그에서 아무 것도 발견하지 못했습니다. 오후 12시 50분에 버튼을 사용하여 다시 시작했습니다. 어떤 로그를 확인할 수 있는지 또는 어떤 아이디어가 있는지 알려주실 수 있나요?
cat /var/log/messages
Dec 10 18:03:50 pve kernel: [ 181.275269] vmbr0: port 2(fwpr105p0) entered
blocking state
Dec 10 18:03:50 pve kernel: [ 181.275271] vmbr0: port 2(fwpr105p0) entered disabled state
Dec 10 18:03:50 pve kernel: [ 181.275331] device fwpr105p0 entered promiscuous mode
Dec 10 18:03:50 pve kernel: [ 181.275358] vmbr0: port 2(fwpr105p0) entered blocking state
Dec 10 18:03:50 pve kernel: [ 181.275360] vmbr0: port 2(fwpr105p0) entered forwarding state
Dec 10 18:03:50 pve kernel: [ 181.277620] fwbr105i0: port 2(veth105i0) entered blocking state
Dec 10 18:03:50 pve kernel: [ 181.277621] fwbr105i0: port 2(veth105i0) entered disabled state
Dec 10 18:03:50 pve kernel: [ 181.277672] device veth105i0 entered promiscuous mode
Dec 10 18:03:50 pve kernel: [ 181.351567] eth0: renamed from vethRS2AYN
Dec 10 18:03:50 pve pve-ha-lrm[2245]: <root@pam> end task UPID:pve:000008C8:0000355B:5DEFCFC9:vzstart:105:root@pam: OK
Dec 10 18:03:50 pve kernel: [ 181.648166] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 10 18:03:50 pve kernel: [ 181.648174] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Dec 10 18:03:50 pve kernel: [ 181.648208] fwbr105i0: port 2(veth105i0) entered blocking state
Dec 10 18:03:50 pve kernel: [ 181.648210] fwbr105i0: port 2(veth105i0) entered forwarding state
Dec 11 03:20:53 pve pveupdate[22976]: <root@pam> starting task UPID:pve:000059D3:00334700:5DF05285:aptupdate::root@pam:
Dec 11 03:20:56 pve pveupdate[22976]: <root@pam> end task UPID:pve:000059D3:00334700:5DF05285:aptupdate::root@pam: OK
Dec 11 06:25:13 pve liblogging-stdlog: [origin software="rsyslogd" swVersion="8.24.0" x-pid="1134" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Dec 11 23:54:34 pve pvedaemon[1934]: <root@pam> successful auth for user 'root@pam'
Dec 11 23:54:40 pve pvedaemon[1934]: <root@pam> starting task UPID:pve:000039B8:00A43BC4:5DF173B0:qmstart:114:root@pam:
Dec 11 23:54:41 pve kernel: [107633.572724] device tap114i0 entered promiscuous mode
Dec 11 23:54:41 pve kernel: [107633.593096] fwbr114i0: port 1(fwln114i0) entered blocking state
Dec 11 23:54:41 pve kernel: [107633.593097] fwbr114i0: port 1(fwln114i0) entered disabled state
Dec 11 23:54:41 pve kernel: [107633.593157] device fwln114i0 entered promiscuous mode
Dec 11 23:54:41 pve kernel: [107633.593186] fwbr114i0: port 1(fwln114i0) entered blocking state
Dec 11 23:54:41 pve kernel: [107633.593188] fwbr114i0: port 1(fwln114i0) entered forwarding state
Dec 11 23:54:41 pve kernel: [107633.595855] vmbr0: port 3(fwpr114p0) entered blocking state
Dec 11 23:54:41 pve kernel: [107633.595857] vmbr0: port 3(fwpr114p0) entered disabled state
Dec 11 23:54:41 pve kernel: [107633.595921] device fwpr114p0 entered promiscuous mode
Dec 11 23:54:41 pve kernel: [107633.595936] vmbr0: port 3(fwpr114p0) entered blocking state
Dec 11 23:54:41 pve kernel: [107633.595937] vmbr0: port 3(fwpr114p0) entered forwarding state
Dec 11 23:54:41 pve kernel: [107633.598134] fwbr114i0: port 2(tap114i0) entered blocking state
Dec 11 23:54:41 pve kernel: [107633.598136] fwbr114i0: port 2(tap114i0) entered disabled state
Dec 11 23:54:41 pve kernel: [107633.598194] fwbr114i0: port 2(tap114i0) entered blocking state
Dec 11 23:54:41 pve kernel: [107633.598195] fwbr114i0: port 2(tap114i0) entered forwarding state
Dec 11 23:54:41 pve pvedaemon[1934]: <root@pam> end task UPID:pve:000039B8:00A43BC4:5DF173B0:qmstart:114:root@pam: OK
Dec 12 00:09:28 pve pvedaemon[1934]: <root@pam> successful auth for user 'root@pam'
Dec 12 00:24:29 pve pvedaemon[1935]: <root@pam> successful auth for user 'root@pam'
Dec 12 00:39:30 pve pvedaemon[1936]: <root@pam> successful auth for user 'root@pam'
Dec 12 00:54:31 pve pvedaemon[1934]: <root@pam> successful auth for user 'root@pam'
Dec 12 01:09:32 pve pvedaemon[1934]: <root@pam> successful auth for user 'root@pam'
Dec 12 01:24:32 pve pvedaemon[31249]: <root@pam> successful auth for user 'root@pam'
Dec 12 01:39:33 pve pvedaemon[31249]: <root@pam> successful auth for user 'root@pam'
Dec 12 01:54:34 pve pvedaemon[1521]: <root@pam> successful auth for user 'root@pam'
Dec 12 02:09:35 pve pvedaemon[31283]: <root@pam> successful auth for user 'root@pam'
Dec 12 02:24:36 pve pvedaemon[1521]: <root@pam> successful auth for user 'root@pam'
Dec 12 02:39:37 pve pvedaemon[31249]: <root@pam> successful auth for user 'root@pam'
Dec 12 04:42:01 pve pveupdate[7733]: <root@pam> starting task UPID:pve:00001E5C:00BE8A77:5DF1B709:aptupdate::root@pam:
Dec 12 04:42:03 pve pveupdate[7733]: <root@pam> end task UPID:pve:00001E5C:00BE8A77:5DF1B709:aptupdate::root@pam: OK
Dec 12 06:25:05 pve liblogging-stdlog: [origin software="rsyslogd" swVersion="8.24.0" x-pid="1134" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Dec 12 12:50:45 pve kernel: [ 0.000000] Linux version 4.15.18-23-pve (build@pve) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP PVE 4.15.18-51 (Wed, 13 Nov 2019 11:20:34 +0100) ()
Dec 12 12:50:45 pve kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.18-23-pve root=/dev/mapper/pve-root ro quiet amd_iommu=on
Dec 12 12:50:45 pve kernel: [ 0.000000] KERNEL supported cpus:
Dec 12 12:50:45 pve kernel: [ 0.000000] Intel GenuineIntel
감사해요
답변1
문제는 RAM에서 발생했습니다. 방금 memtest를 수행했는데 7일 이후로 시스템이 다운되지 않았습니다.