Proxmox restarts randomly

S

SaveMi

New Member
Dec 10, 2023
4
0
1
Hello does anyone knows why my Proxmox server restarts randomly. I have no idea on how to troubleshoot this issue.
This is from the syslog prior to the reboot. Any help would be much much appreciated.

Code: 
Dec 11 17:21:03 proxmox spiceproxy[1069]: worker 1070 started
Dec 11 17:21:03 proxmox systemd[1]: Started spiceproxy.service - PVE SPICE Proxy Server.
Dec 11 17:21:03 proxmox pve-ha-lrm[1071]: starting server
Dec 11 17:21:03 proxmox pve-ha-lrm[1071]: status change startup => wait_for_agent_lock
Dec 11 17:21:03 proxmox systemd[1]: Started pve-ha-lrm.service - PVE Local HA Resource Manager Daemon.
Dec 11 17:21:03 proxmox systemd[1]: Starting pve-guests.service - PVE guests...
Dec 11 17:21:04 proxmox pve-guests[1073]: <root@pam> starting task UPID:proxmox:00000432:0000041C:6576D480:startall::root@pam:
Dec 11 17:21:04 proxmox pvesh[1073]: Starting VM 100
Dec 11 17:21:04 proxmox pve-guests[1074]: <root@pam> starting task UPID:proxmox:00000433:0000041D:6576D480:qmstart:100:root@pam:
Dec 11 17:21:04 proxmox pve-guests[1075]: start VM 100: UPID:proxmox:00000433:0000041D:6576D480:qmstart:100:root@pam:
Dec 11 17:21:04 proxmox systemd[1]: systemd-rfkill.service: Deactivated successfully.
Dec 11 17:21:04 proxmox kernel: kvm[1076]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Dec 11 17:21:04 proxmox systemd[1]: Created slice qemu.slice - Slice /qemu.
Dec 11 17:21:04 proxmox systemd[1]: Started 100.scope.
Dec 11 17:21:05 proxmox kernel: tap100i0: entered promiscuous mode
Dec 11 17:21:05 proxmox kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Dec 11 17:21:05 proxmox kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Dec 11 17:21:05 proxmox kernel: fwpr100p0: entered allmulticast mode
Dec 11 17:21:05 proxmox kernel: fwpr100p0: entered promiscuous mode
Dec 11 17:21:05 proxmox kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Dec 11 17:21:05 proxmox kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Dec 11 17:21:05 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Dec 11 17:21:05 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Dec 11 17:21:05 proxmox kernel: fwln100i0: entered allmulticast mode
Dec 11 17:21:05 proxmox kernel: fwln100i0: entered promiscuous mode
Dec 11 17:21:05 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Dec 11 17:21:05 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Dec 11 17:21:05 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Dec 11 17:21:05 proxmox kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Dec 11 17:21:05 proxmox kernel: tap100i0: entered allmulticast mode
Dec 11 17:21:05 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Dec 11 17:21:05 proxmox kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Dec 11 17:21:05 proxmox kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
Dec 11 17:21:05 proxmox kernel: cp210x 3-1:1.0: device disconnected
Dec 11 17:21:08 proxmox pve-guests[1073]: <root@pam> end task UPID:proxmox:00000432:0000041C:6576D480:startall::root@pam: OK
Dec 11 17:21:08 proxmox systemd[1]: Finished pve-guests.service - PVE guests.
Dec 11 17:21:08 proxmox systemd[1]: Starting pvescheduler.service - Proxmox VE scheduler...
Dec 11 17:21:09 proxmox pvescheduler[1178]: starting server
Dec 11 17:21:09 proxmox systemd[1]: Started pvescheduler.service - Proxmox VE scheduler.
Dec 11 17:21:09 proxmox systemd[1]: Reached target multi-user.target - Multi-User System.
Dec 11 17:21:09 proxmox systemd[1]: Reached target graphical.target - Graphical Interface.
Dec 11 17:21:09 proxmox systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...
Dec 11 17:21:09 proxmox systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Dec 11 17:21:09 proxmox systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
Dec 11 17:21:09 proxmox systemd[1]: Startup finished in 12.901s (firmware) + 5.251s (loader) + 4.154s (kernel) + 10.921s (userspace) = 33.228s.
Dec 11 17:21:10 proxmox chronyd[859]: Selected source 106.10.186.201 (2.debian.pool.ntp.org)
Dec 11 17:21:10 proxmox chronyd[859]: System clock TAI offset set to 37 seconds
Dec 11 17:21:11 proxmox kernel: usb 3-1: reset full-speed USB device number 2 using xhci_hcd
Dec 11 17:21:28 proxmox systemd[1]: systemd-fsckd.service: Deactivated successfully.
Dec 11 17:22:17 proxmox chronyd[859]: Selected source 137.184.250.82 (2.debian.pool.ntp.org)
Dec 11 17:26:35 proxmox chronyd[859]: Selected source 106.10.186.201 (2.debian.pool.ntp.org)
Dec 11 17:36:36 proxmox systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
Dec 11 17:36:36 proxmox systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Dec 11 17:36:36 proxmox systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Dec 11 17:36:36 proxmox systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
-- Reboot --
Dec 11 18:00:55 proxmox kernel: Linux version 6.5.11-7-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-7 (2023-12-05T09:44Z) ()
Dec 11 18:00:55 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.11-7-pve root=/dev/mapper/pve-root ro quiet
Dec 11 18:00:55 proxmox kernel: KERNEL supported cpus:
Dec 11 18:00:55 proxmox kernel:   Intel GenuineIntel
Dec 11 18:00:55 proxmox kernel:   AMD AuthenticAMD
Dec 11 18:00:55 proxmox kernel:   Hygon HygonGenuine
Dec 11 18:00:55 proxmox kernel:   Centaur CentaurHauls
Dec 11 18:00:55 proxmox kernel:   zhaoxin   Shanghai 
Dec 11 18:00:55 proxmox kernel: BIOS-provided physical RAM map:
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009e01fff] usable
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x0000000009e02000-0x0000000009ffffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x000000000a20e000-0x000000000affffff] usable
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000db117fff] usable
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000db118000-0x00000000db497fff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000db498000-0x00000000db4fbfff] ACPI data
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000db4fc000-0x00000000dcbfafff] ACPI NVS
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000dcbfb000-0x00000000ddb4afff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000ddb4b000-0x00000000ddbfefff] type 20
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000ddbff000-0x00000000deffffff] usable
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd7fffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x0000000100000000-0x000000041f37ffff] usable
Dec 11 18:00:55 proxmox kernel: BIOS-e820: [mem 0x000000041f380000-0x000000041fffffff] reserved
Dec 11 18:00:55 proxmox kernel: NX (Execute Disable) protection: active
 
Hello, singlenode or cluster? If cluster please post:
  • cat /etc/pve/corosync.conf
  • cat /etc/hosts
  • cat /etc/network/interfaces
And also post.
  • journalctl | grep corosync
 
Last edited:
jsterr said:
Hello, singlenode or cluster? If cluster please post:
  • cat /etc/pve/corosync.conf
  • cat /etc/hosts
  • cat /etc/network/interfaces
And also post.
  • journalctl | grep corosync
Click to expand...
singlenode sir. I did a "journalctl | grep corosync" and this is the result


Code: 
root@proxmox:~# journalctl | grep corosync
Dec 01 00:33:24 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 01 03:14:30 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 01 05:55:14 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 01 06:41:21 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 01 06:47:29 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 01 13:51:02 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 01 17:56:49 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 02 04:32:25 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 02 06:06:09 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 02 06:06:55 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 02 07:47:56 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 02 13:12:15 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 02 13:50:01 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 02 19:25:32 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 03 09:18:20 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 03 10:18:53 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 03 12:24:41 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 04 01:38:36 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 04 11:38:30 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 04 12:07:47 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 04 21:37:00 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 04 22:55:46 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 05 05:40:35 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 05 17:35:34 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 05 21:05:50 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 06 03:39:36 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 06 06:53:33 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 06 09:59:46 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 06 11:19:43 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 06 13:48:50 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 06 21:33:40 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 07 02:29:08 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 07 08:35:25 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 07 10:36:50 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 07 21:51:35 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 08 03:45:34 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 08 04:42:50 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 08 04:43:33 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 08 09:40:41 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 08 12:55:08 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 08 15:07:45 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 08 19:51:36 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 08 22:52:10 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 09 13:11:01 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 09 16:28:59 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 09 23:02:49 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 00:11:07 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 01:09:33 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 01:49:30 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 02:34:17 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 06:40:56 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 07:51:27 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 09:02:44 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 16:14:34 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 16:16:36 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 16:25:17 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 16:54:26 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 17:08:05 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 17:12:35 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 18:36:13 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 10 18:54:29 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 11 02:26:57 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 11 03:55:54 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 11 12:09:53 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 11 17:21:01 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 11 18:00:58 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
root@proxmox:~#
 
If its a singlehost its very likely that you have broken hardware. The checks from my post are for clusters

"If cluster please post"
Click to expand...
Check ipmi or bmc eventlog, do a memtest, or try to use stress-tool to see if you can reproduce the failure. If yes, something in your hardware is broken, most likely memory.
 
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