Need help, My installation has failed

P

powerpcme

New Member
Dec 20, 2023
3
0
1
This morning while I was running an update on a VM running on this proxmox instance, This instance also runs my router PFsense. Suddenly my network goes down, Which means most likely my vms have failed. Now when I can't connect to the web interface, and when i run `journalctl -f` I get this output in the attached file, here's a small chunk

Code: 
Dec 20 13:33:49 proxmox systemd[1]: rrdcached.service: Failed with result 'exit-code'.
Dec 20 13:33:49 proxmox systemd[1]: Failed to start rrdcached.service - LSB: start or stop rrdcached.
Dec 20 13:33:49 proxmox systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Dec 20 13:33:49 proxmox pmxcfs[6132]: [96B blob data]
Dec 20 13:33:49 proxmox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=127/n/a
Dec 20 13:33:49 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Dec 20 13:33:49 proxmox systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Dec 20 13:33:49 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 20 13:33:49 proxmox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
Dec 20 13:33:49 proxmox systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Dec 20 13:33:49 proxmox systemd[1]: Starting rrdcached.service - LSB: start or stop rrdcached...
Dec 20 13:33:49 proxmox rrdcached[6138]: [99B blob data]
Dec 20 13:33:49 proxmox rrdcached[6134]: rrdcached FAILED ... failed!
Dec 20 13:33:49 proxmox systemd[1]: rrdcached.service: Control process exited, code=exited, status=127/n/a
Dec 20 13:33:49 proxmox systemd[1]: rrdcached.service: Failed with result 'exit-code'.
Dec 20 13:33:49 proxmox systemd[1]: Failed to start rrdcached.service - LSB: start or stop rrdcached.
Dec 20 13:33:49 proxmox systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Dec 20 13:33:49 proxmox pmxcfs[6139]: [96B blob data]
Dec 20 13:33:49 proxmox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=127/n/a
Dec 20 13:33:49 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Dec 20 13:33:49 proxmox systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Dec 20 13:33:49 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 20 13:33:49 proxmox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 4.
Dec 20 13:33:49 proxmox systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Dec 20 13:33:49 proxmox systemd[1]: Starting rrdcached.service - LSB: start or stop rrdcached...
Dec 20 13:33:49 proxmox rrdcached[6144]: [99B blob data]
Dec 20 13:33:49 proxmox rrdcached[6140]: rrdcached FAILED ... failed!
Dec 20 13:33:49 proxmox systemd[1]: rrdcached.service: Control process exited, code=exited, status=127/n/a
Dec 20 13:33:49 proxmox systemd[1]: rrdcached.service: Failed with result 'exit-code'.
Dec 20 13:33:49 proxmox systemd[1]: Failed to start rrdcached.service - LSB: start or stop rrdcached.
Dec 20 13:33:49 proxmox systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Dec 20 13:33:49 proxmox pmxcfs[6145]: [96B blob data]
Dec 20 13:33:49 proxmox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=127/n/a
Dec 20 13:33:49 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Dec 20 13:33:49 proxmox systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Dec 20 13:33:49 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 20 13:33:49 proxmox pvedaemon[6120]: [206B blob data]
Dec 20 13:33:49 proxmox pvedaemon[6120]:  at /usr/share/perl5/PVE/RRD.pm line 5.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/RRD.pm line 5.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/RRD.pm line 5.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/API2/Qemu.pm line 18.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Qemu.pm line 18.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 18.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 21.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 22.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 22.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 15.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 15.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 15.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Dec 20 13:33:49 proxmox systemd[1]: pvedaemon.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Dec 20 13:33:49 proxmox systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Dec 20 13:33:49 proxmox systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
Dec 20 13:33:49 proxmox systemd[1]: pvedaemon.service: Consumed 1.046s CPU time.
Dec 20 13:33:50 proxmox systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Dec 20 13:33:50 proxmox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Dec 20 13:33:50 proxmox systemd[1]: pvedaemon.service: Scheduled restart job, restart counter is at 1.
Dec 20 13:33:50 proxmox systemd[1]: Stopped pvedaemon.service - PVE API Daemon.
Dec 20 13:33:50 proxmox systemd[1]: pvedaemon.service: Consumed 1.046s CPU time.
Dec 20 13:33:50 proxmox systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Dec 20 13:33:50 proxmox systemd[1]: rrdcached.service: Start request repeated too quickly.
Dec 20 13:33:50 proxmox systemd[1]: rrdcached.service: Failed with result 'exit-code'.
Dec 20 13:33:50 proxmox systemd[1]: Failed to start rrdcached.service - LSB: start or stop rrdcached.
Dec 20 13:33:50 proxmox systemd[1]: pve-cluster.service: Start request repeated too quickly.
Dec 20 13:33:50 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Dec 20 13:33:50 proxmox systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
Dec 20 13:33:50 proxmox systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Dec 20 13:33:50 proxmox systemd[1]: Starting pvedaemon.service - PVE API Daemon...
Dec 20 13:33:50 proxmox pvecm[6146]: ipcc_send_rec[1] failed: Connection refused
Dec 20 13:33:50 proxmox pvecm[6146]: ipcc_send_rec[2] failed: Connection refused
Dec 20 13:33:50 proxmox pvecm[6146]: ipcc_send_rec[3] failed: Connection refused
Dec 20 13:33:50 proxmox pvecm[6146]: Unable to load access control list: Connection refused
Dec 20 13:33:51 proxmox pvedaemon[6147]: [206B blob data]

At the very least if I can get my pfsense disk image out I will do that but id rather try to fix this. Thanks!
 

Attachments

  • prox-fail.txt
    36.8 KB · Views: 2
Are you using a clustered setup? (looks like it from the log at least)
unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf)
Looks like your cluster config is missing (or the path to it is offline).
 
J-dub said:
Are you using a clustered setup? (looks like it from the log at least)
unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf)
Looks like your cluster config is missing (or the path to it is offline).
Click to expand...
Nope was just a single machine
 
Starting pvedaemon.service - PVE API Daemon...
Dec 20 13:33:50 proxmox pvecm[6146]: ipcc_send_rec[1] failed: Connection refused
The error message indicates that the service is unable to start because it is unable to establish a connection with the corosync service.

unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf is preventing that service from starting.

Can you open it in nano /etc/corosync/corosync.conf ?
 
1703110085405.png

That file doesn't seem to exist
J-dub said:
Starting pvedaemon.service - PVE API Daemon...
Dec 20 13:33:50 proxmox pvecm[6146]: ipcc_send_rec[1] failed: Connection refused
The error message indicates that the service is unable to start because it is unable to establish a connection with the corosync service.

unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf is preventing that service from starting.

Can you open it in nano /etc/corosync/corosync.conf ?
Click to expand...
 
Well you "can" make that file - but I don't want to lead you down the wrong path, if that isn't the correct fix for your situation. It's blind leading the blind with you and I.
It's odd that it's looking to load a cluster config file as a single node server. It's not really surprising that it can't find (since it's a solo server) the file. That's what your logs are showing however.. PVEdaemon service isn't starting because it's not able to find the access it needs from the corosync.conf file.
You're going to have wait until someone who know more about it responds - or - risk screwing everything up and try to create the the file it's looking for.
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_corosync_configuration
systemctl restart corosync
Good Luck!
:oops:
 
Last edited:
J-dub said:
unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf)
Looks like your cluster config is missing (or the path to it is offline).
Click to expand...
That's normal for single node clusters and nothing to worry about. No need for creating that file.

J-dub said:
Dec 20 13:33:50 proxmox pvecm[6146]: ipcc_send_rec[1] failed: Connection refused
The error message indicates that the service is unable to start because it is unable to establish a connection with the corosync service.
Click to expand...
More likely that the error message is due to pmxcfs (pve-cluster) not running.

Seems like the issue lies with failed compilation in perl code:
Code: 
Dec 20 13:33:49 proxmox pvedaemon[6120]: [206B blob data]
Dec 20 13:33:49 proxmox pvedaemon[6120]:  at /usr/share/perl5/PVE/RRD.pm line 5.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/RRD.pm line 5.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/RRD.pm line 5.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/API2/Qemu.pm line 18.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Qemu.pm line 18.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 18.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 21.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 22.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 22.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 15.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 15.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 15.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Dec 20 13:33:49 proxmox pvedaemon[6120]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Dec 20 13:33:49 proxmox pvedaemon[6120]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.

This is usually caused either by a failed / partial upgrade or corrupted packages.

You can try upgrading the packages of the node:
Code: 
apt update && apt dist-upgrade

If that doesn't help, you can check for problems with packages via the following command:
Code: 
debsums -s
 
Last edited:
  • Like
Reactions: J-dub
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
Back