Proxmox dont initialize

rihanalkamim

New Member
Aug 22, 2023
4
0
1
Don't start web services and has many errors
Can help me?

WhatsApp Image 2023-08-22 at 09.23.15.jpeg


Code:
root@pvlibra:~# systemctl status pve-cluster.service corosync.service
● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor p>
     Active: failed (Result: exit-code) since Tue 2023-08-22 03:57:53 -03; 5h 2>
    Process: 36165 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
        CPU: 5ms

Warning: journal has been rotated since unit was started, output may be incompl>

● corosync.service - Corosync Cluster Engine
     Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor pres>
     Active: inactive (dead)
  Condition: start condition failed at Tue 2023-08-22 03:57:53 -03; 5h 27min ago
             └─ ConditionPathExists=/etc/corosync/corosync.conf was not met
       Docs: man:corosync
             man:corosync.conf
             man:corosync_overview
...skipping...
● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor p>
     Active: failed (Result: exit-code) since Tue 2023-08-22 03:57:53 -03; 5h 2>
    Process: 36165 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
        CPU: 5ms

Warning: journal has been rotated since unit was started, output may be incompl>

● corosync.service - Corosync Cluster Engine
     Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor pres>
     Active: inactive (dead)
  Condition: start condition failed at Tue 2023-08-22 03:57:53 -03; 5h 27min ago
             └─ ConditionPathExists=/etc/corosync/corosync.conf was not met
       Docs: man:corosync
             man:corosync.conf
             man:corosync_overview
 
First I would check if your root filesystem is 100% filled and therefore switched to read-only, using df -h via ssh/console.

Edit: And your second screenshot would indicate this too.

In that case try to delete some stuff (logs in /var/log, failed iso uploads in /var/tmp, isos/backups in /var/lib/vz, remove some snapshots, do a fstrim -a, ...) to free up some space.
 
Last edited:
The root filesystem is only using a fraction (94G) of your disk. The other 795G are used as a LVM-Thin pool to store your virtual disks and this isn't part of your root filesystem nor can it store any files.
 

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!

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!