[SOLVED] Proxmox Crash -> Ursache finden

aXu

New Member
Feb 21, 2021
9
1
3
33
Salü zusammen

Ich habe bei mir im Homelab ein Proxmoxserver Eigenbau aufgesetzt. Nur stürzt das ganze unregelmässig ab...
Welches Logfile könnte mir da am einfachsten Auskunft geben? In der Task History steht nix drin.

Welches Logfile unter /var/log muss ich auseinandernehmen?

System:
AsRock AB350M Pro4-F
Ryzen 7 1800X
32GB Ram
m.2 SSD

Board und Ram sind neu.

Grüsse und Danke für jeden Input

Feb 21 19:29:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:29:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:30:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:30:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:30:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:31:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:31:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:31:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:32:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:32:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:32:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:33:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:33:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:33:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:34:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:34:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:34:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:35:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:35:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:35:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:36:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:36:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:36:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:37:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:37:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:37:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:38:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:38:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:38:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:39:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:39:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:39:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:40:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:40:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:40:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:40:13 pve-2U postfix/qmgr[1405]: 5F6B2220514: from=<axu@axu.ch>, size=1190, nrcpt=1 (queue active)
Feb 21 19:40:13 pve-2U postfix/smtp[1118]: 5F6B2220514: host mx2.mail.hostpoint.ch[217.26.49.139] refused to talk to me: 550-rejected because 80.219.160.14 is blacklisted at zen.spamhaus.org.dnslist: 550 https://www.spamhaus.org/query/ip/80.219.160.14
Feb 21 19:40:13 pve-2U postfix/smtp[1118]: 5F6B2220514: to=<axu@axu.ch>, relay=mx1.mail.hostpoint.ch[217.26.49.138]:25, delay=4513, delays=4513/0.01/0.13/0, dsn=4.0.0, status=deferred (host mx1.mail.hostpoint.ch[217.26.49.138] refused to talk to me: 550-rejected because 80.219.160.14 is blacklisted at zen.spamhaus.org.dnslist: 550 https://www.spamhaus.org/query/ip/80.219.160.14)
Feb 21 19:41:00 pve-2U systemd[1]: Starting Proxmox VE replication runner...
Feb 21 19:41:00 pve-2U systemd[1]: pvesr.service: Succeeded.
Feb 21 19:41:00 pve-2U systemd[1]: Started Proxmox VE replication runner.
Feb 21 19:42:03 pve-2U systemd-modules-load[500]: Inserted module 'iscsi_tcp'
Feb 21 19:42:03 pve-2U dmeventd[533]: dmeventd ready for processing.
Feb 21 19:42:03 pve-2U systemd-modules-load[500]: Inserted module 'ib_iser'
Feb 21 19:42:03 pve-2U lvm[533]: Monitoring thin pool pve-data-tpool.
Feb 21 19:42:03 pve-2U systemd-modules-load[500]: Inserted module 'vhost_net'
Feb 21 19:42:03 pve-2U systemd[1]: Starting Flush Journal to Persistent Storage...
Feb 21 19:42:03 pve-2U systemd[1]: Started udev Kernel Device Manager.
Feb 21 19:42:03 pve-2U lvm[511]: 8 logical volume(s) in volume group "pve" monitored
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] Linux version 5.4.78-2-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.4.78-2 (Thu, 03 Dec 2020 14:26:17 +0100) ()
Feb 21 19:42:03 pve-2U systemd[1]: Started Flush Journal to Persistent Storage.
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.78-2-pve root=/dev/mapper/pve-root ro quiet
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] KERNEL supported cpus:
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] Intel GenuineIntel
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] AMD AuthenticAMD
Feb 21 19:42:03 pve-2U systemd[1]: Started udev Coldplug all Devices.
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] Hygon HygonGenuine
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] Centaur CentaurHauls
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] zhaoxin Shanghai
Feb 21 19:42:03 pve-2U systemd[1]: Starting Helper to synchronize boot up for ifupdown...
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Feb 21 19:42:03 pve-2U kernel: [ 0.000000] BIOS-provided physical RAM map:
Feb 21 19:42:03 pve-2U systemd[1]: Starting udev Wait for Complete Device Initialization...

Auszug aus /var/log/syslog
Um 19:40:46 müsste das ganze gecrasht sein, gemäss Ereignisanzeige der Windows VM
Das System wurde zuvor am ‎21.‎02.‎2021 um 19:40:46 unerwartet heruntergefahren.
 
Last edited:

aaron

Proxmox Staff Member
Staff member
Jun 3, 2019
1,753
230
63
Die syslog ist der richtige Ort. Aber in dem Auszug sieht man nicht wirklich was vor dem Neustart. Ist das eine einzelne Node oder betreibst du einen Cluster?
 

aXu

New Member
Feb 21, 2021
9
1
3
33
Salü
Als einzelner Node.
Ja, das ist genau der Punkt: es steht nichts sinnvolles/relevantes im Syslog... Deshalb die Frage ob allenfals ein anderer Ort noch relevant wäre...

Habe Proxmox jetzt nochmal platt gemacht und neu aufgesetzt.. mal sehen ob dies allenfalls etwas bringt..
 
Last edited:

aaron

Proxmox Staff Member
Staff member
Jun 3, 2019
1,753
230
63
Wenn das Problem wieder auftaucht, und wenn es ein HW Problem ist, wird es das wahrscheinlich, kannst du versuchen mal einen RAM Test zu machen. Vielleicht ist dieser defekt. Ansonsten wirds mühsam und wird eher auf ein schrittweises Austauschen der Komponenten hinauslaufen :/
 

aXu

New Member
Feb 21, 2021
9
1
3
33
naja, viel auszutauschen gäbe es nicht mehr oO.
Die CPU ist das einzige Bauteil welches mittlerweile nicht mehr neu ist.
Werde es beobachten wie es weitergeht :)
 

About

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

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 your own in 60 seconds.

Buy now!