Error File config.db

Chicho80

New Member
Jan 13, 2021
1
0
1
32
Good day
I present an error in the config.db file when there was a failure in a disk and it was replaced but a new one but when the server crashed it restarted and the service of pve-cluster.service and pveproxy is not uploading since when checking the status of the 2 services present the following error

root@eridanus:/var/lib/pve-cluster# service pve-cluster status
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2021-01-15 11:23:26 -05; 43min ago
Process: 3303 ExecStart=/usr/bin/pmxcfs (code=exited, status=255)
CPU: 12ms

Jan 15 11:23:26 eridanus pmxcfs[3303]: [database] crit: found strange placeholder for (inode = 000000000000000D, parent = 000000000000000B, name = 'qemu-server', type = '4')
Jan 15 11:23:26 eridanus pmxcfs[3303]: [database] crit: found strange placeholder for (inode = 000000000000000D, parent = 000000000000000B, name = 'qemu-server', type = '4')
Jan 15 11:23:26 eridanus pmxcfs[3303]: [database] crit: DB load failed
Jan 15 11:23:26 eridanus pmxcfs[3303]: [database] crit: DB load failed
Jan 15 11:23:26 eridanus pmxcfs[3303]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jan 15 11:23:26 eridanus pmxcfs[3303]: [main] notice: exit proxmox configuration filesystem (-1)
Jan 15 11:23:26 eridanus systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Jan 15 11:23:26 eridanus systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jan 15 11:23:26 eridanus systemd[1]: pve-cluster.service: Unit entered failed state.
Jan 15 11:23:26 eridanus systemd[1]: pve-cluster.service: Failed with result 'exit-code'.

root@eridanus:/var/lib/pve-cluster# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2021-01-15 11:23:00 -05; 55min ago
Process: 3223 ExecStop=/usr/bin/pveproxy stop (code=exited, status=0/SUCCESS)
Process: 3239 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 3266 (pveproxy)
Tasks: 4 (limit: 4915)
Memory: 123.7M
CPU: 1min 8.292s
CGroup: /system.slice/pveproxy.service
├─3266 pveproxy
├─6437 pveproxy worker
├─6438 pveproxy worker
└─6439 pveproxy worker

Jan 15 12:18:23 eridanus pveproxy[6437]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1647.
Jan 15 12:18:23 eridanus pveproxy[6435]: worker exit
Jan 15 12:18:23 eridanus pveproxy[6436]: worker exit
Jan 15 12:18:23 eridanus pveproxy[3266]: worker 6435 finished
Jan 15 12:18:23 eridanus pveproxy[3266]: worker 6436 finished
Jan 15 12:18:23 eridanus pveproxy[3266]: starting 2 worker(s)
Jan 15 12:18:23 eridanus pveproxy[3266]: worker 6438 started
Jan 15 12:18:23 eridanus pveproxy[3266]: worker 6439 started
Jan 15 12:18:23 eridanus pveproxy[6438]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1647.
Jan 15 12:18:23 eridanus pveproxy[6439]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1647.


I would like to know how I solve the problem to reset the proxmoxVE and be able to upload my virtual machines
 

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!