VM fällt einfach plötzlich aus?

F

fpausp

Renowned Member
Aug 31, 2010
642
44
93
Austria near Vienna
Hab hier eine von zwei gleichen VMs (IPFire Firewall) die in unregelmäßigen Abständen einfach ausfällt:

1631249359811.png

Wie kann man bitte der Sache auf den Grund gehen?
 
dietmar said:
syslogs anschauen...
Click to expand...

QNAP1 war absichtlich aus...

Code: 
Sep 10 00:54:15 pve02 pvestatd[1229]: status update time (7.543 seconds)
Sep 10 00:54:19 pve02 kernel: [315786.547863] show_signal_msg: 7 callbacks suppressed
Sep 10 00:54:19 pve02 kernel: [315786.547867] kvm[1552]: segfault at 140 ip 00005644c7bdbc78 sp 00007fde5a0e0ce8 error 4 in qemu-system-x86_64[5644c76e0000+532000]
Sep 10 00:54:19 pve02 kernel: [315786.547877] Code: eb d3 c5 f5 eb ca c5 f5 eb c0 c4 e2 7d 17 c0 0f 94 c0 c5 f8 77 c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 48 8d 47 50 48 8d 14 37 <f3> 0f 6f 07 48 83 e0 f0 48 83 e2 f0 48 39 d0 76 28 eb 35 0f 1f 44
Sep 10 00:54:19 pve02 kernel: [315786.717325] fwbr201i0: port 2(tap201i0) entered disabled state
Sep 10 00:54:19 pve02 kernel: [315786.717409] fwbr201i0: port 2(tap201i0) entered disabled state
Sep 10 00:54:19 pve02 kernel: [315786.781457] fwbr201i1: port 2(tap201i1) entered disabled state
Sep 10 00:54:19 pve02 kernel: [315786.781526] fwbr201i1: port 2(tap201i1) entered disabled state
Sep 10 00:54:19 pve02 systemd[1]: 201.scope: Succeeded.
Sep 10 00:54:19 pve02 systemd[1]: 201.scope: Consumed 5h 29min 12.351s CPU time.
Sep 10 00:54:20 pve02 qmeventd[2509950]: Starting cleanup for 201
Sep 10 00:54:20 pve02 kernel: [315787.525411] fwbr201i1: port 1(fwln201i1) entered disabled state
Sep 10 00:54:20 pve02 kernel: [315787.525470] vmbr5: port 2(fwpr201p1) entered disabled state
Sep 10 00:54:20 pve02 kernel: [315787.525545] device fwln201i1 left promiscuous mode
Sep 10 00:54:20 pve02 kernel: [315787.525547] fwbr201i1: port 1(fwln201i1) entered disabled state
Sep 10 00:54:20 pve02 kernel: [315787.545365] device fwpr201p1 left promiscuous mode
Sep 10 00:54:20 pve02 kernel: [315787.545370] vmbr5: port 2(fwpr201p1) entered disabled state
Sep 10 00:54:20 pve02 kernel: [315787.659903] fwbr201i0: port 1(fwln201i0) entered disabled state
Sep 10 00:54:20 pve02 kernel: [315787.659956] vmbr2: port 3(fwpr201p0) entered disabled state
Sep 10 00:54:20 pve02 kernel: [315787.660013] device fwln201i0 left promiscuous mode
Sep 10 00:54:20 pve02 kernel: [315787.660015] fwbr201i0: port 1(fwln201i0) entered disabled state
Sep 10 00:54:20 pve02 kernel: [315787.677376] device fwpr201p0 left promiscuous mode
Sep 10 00:54:20 pve02 kernel: [315787.677381] vmbr2: port 3(fwpr201p0) entered disabled state
Sep 10 00:54:20 pve02 qmeventd[2509950]: Finished cleanup for 201

Sep 10 00:54:53 pve02 pvestatd[1229]: status update time (6.577 seconds)
Sep 10 00:55:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Sep 10 00:55:04 pve02 systemd[1]: pvesr.service: Succeeded.
Sep 10 00:55:04 pve02 systemd[1]: Finished Proxmox VE replication runner.
Sep 10 00:55:05 pve02 pvestatd[1229]: storage 'QNAP1' is not online

Sep 10 00:55:54 pve02 pvestatd[1229]: status update time (6.953 seconds)
Sep 10 00:56:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Sep 10 00:56:01 pve02 systemd[1]: pvesr.service: Succeeded.
Sep 10 00:56:01 pve02 systemd[1]: Finished Proxmox VE replication runner.

Sep 10 00:56:54 pve02 pvestatd[1229]: status update time (7.223 seconds)
Sep 10 00:57:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Sep 10 00:57:01 pve02 systemd[1]: pvesr.service: Succeeded.
Sep 10 00:57:01 pve02 systemd[1]: Finished Proxmox VE replication runner.

Sep 10 00:57:54 pve02 pvestatd[1229]: status update time (6.802 seconds)
Sep 10 00:58:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Sep 10 00:58:01 pve02 systemd[1]: pvesr.service: Succeeded.
Sep 10 00:58:01 pve02 systemd[1]: Finished Proxmox VE replication runner.

Sep 10 00:58:46 pve02 pvestatd[1229]: status update time (8.235 seconds)
Sep 10 00:58:53 pve02 pvestatd[1229]: storage 'QNAP1' is not online
Sep 10 00:58:53 pve02 pvestatd[1229]: status update time (6.577 seconds)
Sep 10 00:59:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Sep 10 00:59:01 pve02 systemd[1]: pvesr.service: Succeeded.
Sep 10 00:59:01 pve02 systemd[1]: Finished Proxmox VE replication runner.
Sep 10 00:59:03 pve02 pvestatd[1229]: storage 'QNAP1' is not online

Sep 10 01:00:54 pve02 pvestatd[1229]: status update time (6.498 seconds)
Sep 10 01:01:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:01:02 pve02 systemd[1]: pvesr.service: Succeeded.
Sep 10 01:01:02 pve02 systemd[1]: Finished Proxmox VE replication runner.
Sep 10 01:01:03 pve02 pvestatd[1229]: storage 'QNAP1' is not online
Sep 10 01:01:04 pve02 pvestatd[1229]: status update time (6.841 seconds)
Sep 10 01:01:13 pve02 pvestatd[1229]: storage 'QNAP1' is not online
Sep 10 01:01:14 pve02 pvestatd[1229]: status update time (6.722 seconds)
Sep 10 01:01:24 pve02 pvestatd[1229]: storage 'QNAP1' is not online
Sep 10 01:01:24 pve02 pvestatd[1229]: status update time (6.689 seconds)
Sep 10 01:01:27 pve02 kernel: [316214.492996] fwbr231i0: port 2(tap231i0) entered disabled state
Sep 10 01:01:27 pve02 kernel: [316214.507933] fwbr231i0: port 1(fwln231i0) entered disabled state
Sep 10 01:01:27 pve02 kernel: [316214.507980] vmbr1: port 3(fwpr231p0) entered disabled state
Sep 10 01:01:27 pve02 kernel: [316214.508173] device fwln231i0 left promiscuous mode
Sep 10 01:01:27 pve02 kernel: [316214.508178] fwbr231i0: port 1(fwln231i0) entered disabled state
Sep 10 01:01:27 pve02 kernel: [316214.533846] device fwpr231p0 left promiscuous mode
Sep 10 01:01:27 pve02 kernel: [316214.533848] vmbr1: port 3(fwpr231p0) entered disabled state
Sep 10 01:01:27 pve02 qmeventd[778]: read: Connection reset by peer
Sep 10 01:01:27 pve02 systemd[1]: 231.scope: Succeeded.
Sep 10 01:01:27 pve02 systemd[1]: 231.scope: Consumed 2min 6.473s CPU time.
Sep 10 01:01:27 pve02 vzdump[2481376]: INFO: Finished Backup of VM 231 (00:07:18)
Sep 10 01:01:27 pve02 vzdump[2481376]: INFO: Starting Backup of VM 232 (qemu)
Sep 10 01:01:28 pve02 systemd[1]: Started 232.scope.
Sep 10 01:01:28 pve02 qmeventd[2513100]: Starting cleanup for 231
Sep 10 01:01:28 pve02 qmeventd[2513100]: Finished cleanup for 231
Sep 10 01:01:29 pve02 systemd-udevd[2513096]: Using default interface naming scheme 'v247'.
Sep 10 01:01:29 pve02 systemd-udevd[2513096]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 10 01:01:29 pve02 kernel: [316217.171696] device tap232i0 entered promiscuous mode
Sep 10 01:01:29 pve02 systemd-udevd[2513068]: Using default interface naming scheme 'v247'.
Sep 10 01:01:29 pve02 systemd-udevd[2513068]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 10 01:01:29 pve02 systemd-udevd[2513068]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 10 01:01:29 pve02 systemd-udevd[2513096]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 10 01:01:29 pve02 kernel: [316217.204806] fwbr232i0: port 1(fwln232i0) entered blocking state
Sep 10 01:01:29 pve02 kernel: [316217.204811] fwbr232i0: port 1(fwln232i0) entered disabled state
Sep 10 01:01:29 pve02 kernel: [316217.204865] device fwln232i0 entered promiscuous mode
Sep 10 01:01:29 pve02 kernel: [316217.204902] fwbr232i0: port 1(fwln232i0) entered blocking state
Sep 10 01:01:29 pve02 kernel: [316217.204904] fwbr232i0: port 1(fwln232i0) entered forwarding state
Sep 10 01:01:29 pve02 kernel: [316217.208637] vmbr1: port 3(fwpr232p0) entered blocking state
Sep 10 01:01:29 pve02 kernel: [316217.208642] vmbr1: port 3(fwpr232p0) entered disabled state
Sep 10 01:01:29 pve02 kernel: [316217.208692] device fwpr232p0 entered promiscuous mode
Sep 10 01:01:29 pve02 kernel: [316217.208710] vmbr1: port 3(fwpr232p0) entered blocking state
Sep 10 01:01:29 pve02 kernel: [316217.208712] vmbr1: port 3(fwpr232p0) entered forwarding state
Sep 10 01:01:29 pve02 kernel: [316217.212286] fwbr232i0: port 2(tap232i0) entered blocking state
Sep 10 01:01:29 pve02 kernel: [316217.212291] fwbr232i0: port 2(tap232i0) entered disabled state
Sep 10 01:01:29 pve02 kernel: [316217.212354] fwbr232i0: port 2(tap232i0) entered blocking state
Sep 10 01:01:29 pve02 kernel: [316217.212356] fwbr232i0: port 2(tap232i0) entered forwarding state

Sep 10 01:01:55 pve02 pvestatd[1229]: status update time (7.832 seconds)
Sep 10 01:02:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:02:02 pve02 systemd[1]: pvesr.service: Succeeded.
Sep 10 01:02:02 pve02 systemd[1]: Finished Proxmox VE replication runner.
Sep 10 01:02:04 pve02 pvestatd[1229]: storage 'QNAP1' is not online

Sep 10 01:05:54 pve02 pvestatd[1229]: storage 'QNAP1' is not online
Sep 10 01:05:54 pve02 pvestatd[1229]: status update time (6.906 seconds)
Sep 10 01:06:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:06:01 pve02 systemd[1]: pvesr.service: Succeeded.
Sep 10 01:06:01 pve02 systemd[1]: Finished Proxmox VE replication runner.
Sep 10 01:06:03 pve02 pvestatd[1229]: storage 'QNAP1' is not online
Sep 10 01:06:04 pve02 pvestatd[1229]: status update time (6.544 seconds)
Sep 10 01:06:13 pve02 kernel: [316500.566787] fwbr232i0: port 2(tap232i0) entered disabled state
Sep 10 01:06:13 pve02 kernel: [316500.582768] fwbr232i0: port 1(fwln232i0) entered disabled state
Sep 10 01:06:13 pve02 kernel: [316500.582816] vmbr1: port 3(fwpr232p0) entered disabled state
Sep 10 01:06:13 pve02 kernel: [316500.582882] device fwln232i0 left promiscuous mode
Sep 10 01:06:13 pve02 kernel: [316500.582884] fwbr232i0: port 1(fwln232i0) entered disabled state
Sep 10 01:06:13 pve02 kernel: [316500.600601] device fwpr232p0 left promiscuous mode
Sep 10 01:06:13 pve02 kernel: [316500.600604] vmbr1: port 3(fwpr232p0) entered disabled state
Sep 10 01:06:13 pve02 qmeventd[778]: read: Connection reset by peer
Sep 10 01:06:13 pve02 systemd[1]: 232.scope: Succeeded.
Sep 10 01:06:13 pve02 systemd[1]: 232.scope: Consumed 3min 26.985s CPU time.
Sep 10 01:06:13 pve02 pvestatd[1229]: storage 'QNAP1' is not online
Sep 10 01:06:13 pve02 pvestatd[1229]: status update time (6.571 seconds)
Sep 10 01:06:14 pve02 qmeventd[2514969]: Starting cleanup for 232
Sep 10 01:06:14 pve02 qmeventd[2514969]: Finished cleanup for 232
Sep 10 01:06:14 pve02 vzdump[2481376]: INFO: Finished Backup of VM 232 (00:04:47)
Sep 10 01:06:14 pve02 vzdump[2481376]: INFO: Starting Backup of VM 233 (qemu)
Sep 10 01:06:14 pve02 systemd[1]: Started 233.scope.
Sep 10 01:06:14 pve02 systemd-udevd[2514965]: Using default interface naming scheme 'v247'.
Sep 10 01:06:14 pve02 systemd-udevd[2514965]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 10 01:06:15 pve02 kernel: [316502.962880] device tap233i0 entered promiscuous mode
Sep 10 01:06:15 pve02 systemd-udevd[2514957]: Using default interface naming scheme 'v247'.
Sep 10 01:06:15 pve02 systemd-udevd[2514957]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 10 01:06:15 pve02 systemd-udevd[2514957]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 10 01:06:15 pve02 systemd-udevd[2514965]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Sep 10 01:06:15 pve02 kernel: [316502.995600] fwbr233i0: port 1(fwln233i0) entered blocking state
Sep 10 01:06:15 pve02 kernel: [316502.995605] fwbr233i0: port 1(fwln233i0) entered disabled state
Sep 10 01:06:15 pve02 kernel: [316502.995657] device fwln233i0 entered promiscuous mode
Sep 10 01:06:15 pve02 kernel: [316502.995710] fwbr233i0: port 1(fwln233i0) entered blocking state
Sep 10 01:06:15 pve02 kernel: [316502.995711] fwbr233i0: port 1(fwln233i0) entered forwarding state
Sep 10 01:06:15 pve02 kernel: [316502.999415] vmbr3: port 3(fwpr233p0) entered blocking state
Sep 10 01:06:15 pve02 kernel: [316502.999419] vmbr3: port 3(fwpr233p0) entered disabled state
Sep 10 01:06:15 pve02 kernel: [316502.999471] device fwpr233p0 entered promiscuous mode
Sep 10 01:06:15 pve02 kernel: [316502.999489] vmbr3: port 3(fwpr233p0) entered blocking state
Sep 10 01:06:15 pve02 kernel: [316502.999491] vmbr3: port 3(fwpr233p0) entered forwarding state
Sep 10 01:06:15 pve02 kernel: [316503.003184] fwbr233i0: port 2(tap233i0) entered blocking state
Sep 10 01:06:15 pve02 kernel: [316503.003188] fwbr233i0: port 2(tap233i0) entered disabled state
Sep 10 01:06:15 pve02 kernel: [316503.003252] fwbr233i0: port 2(tap233i0) entered blocking state
Sep 10 01:06:15 pve02 kernel: [316503.003254] fwbr233i0: port 2(tap233i0) entered forwarding state

Sep 10 01:06:54 pve02 pvestatd[1229]: status update time (6.765 seconds)
Sep 10 01:07:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Sep 10 01:07:01 pve02 systemd[1]: pvesr.service: Succeeded.
Sep 10 01:07:01 pve02 systemd[1]: Finished Proxmox VE replication runner.

Sep 10 01:08:03 pve02 pvestatd[1229]: status update time (6.516 seconds)
Sep 10 01:08:05 pve02 systemd[1]: pvesr.service: Succeeded.
Sep 10 01:08:05 pve02 systemd[1]: Finished Proxmox VE replication runner.

Sep 10 01:09:05 pve02 pvestatd[1229]: status update time (8.059 seconds)
Sep 10 01:09:08 pve02 systemd[1]: pvesr.service: Succeeded.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom