Unable to open database after fusebox upgrade.

[Miss Fatale]

Hello, I upgraded my fusebox a few days ago and since my proxmox pvestatd.service and pveproxy.service keep running into errors. I have referenced to an earlier problem this thread. I have tried multiple causes from checking for errors in my /etc/hosts /etc/hostname to manually deleting entries in config.db here are some of the errors and files. also pvedaemon.service runs fine.

/etc/hosts

127.0.0.1 localhost.localdomain localhost
192.168.x.xx missfatale.com kerrigan

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

journalctl -b -u pve-cluster

Jun 28 14:03:25 kerrigan pmxcfs[1911]: [database] crit: found entry with duplicate name 'qemu-server' - A:(inode = 0x00000000018F6C0D, parent = 0x00000000018F6C0C, v./mtime = 0x18F6C0D/0x1683123305) vs. B:(inode = 0x00000000018F6D3B, parent = >
Jun 28 14:03:25 kerrigan pmxcfs[1911]: [database] crit: found entry with duplicate name 'qemu-server' - A:(inode = 0x00000000018F6C0D, parent = 0x00000000018F6C0C, v./mtime = 0x18F6C0D/0x1683123305) vs. B:(inode = 0x00000000018F6D3B, parent = >
Jun 28 14:03:25 kerrigan pmxcfs[1911]: [database] crit: DB load failed
Jun 28 14:03:25 kerrigan pmxcfs[1911]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jun 28 14:03:25 kerrigan pmxcfs[1911]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 28 14:03:25 kerrigan pmxcfs[1911]: [database] crit: DB load failed
Jun 28 14:03:25 kerrigan pmxcfs[1911]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jun 28 14:03:25 kerrigan pmxcfs[1911]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 28 14:03:25 kerrigan systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 28 14:03:25 kerrigan systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 28 14:03:25 kerrigan systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 28 14:03:25 kerrigan systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jun 28 14:03:25 kerrigan systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 28 14:03:25 kerrigan systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jun 28 14:03:25 kerrigan systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 28 14:03:25 kerrigan systemd[1]: Failed to start The Proxmox VE cluster filesystem.

systemctl status pvestatd.service

● pvestatd.service - PVE Status Daemon
     Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2023-06-28 14:03:24 CEST; 3min 30s ago
    Process: 1804 ExecStart=/usr/bin/pvestatd start (code=exited, status=111)
        CPU: 549ms

Jun 28 14:03:24 kerrigan pvestatd[1804]: ipcc_send_rec[1] failed: Connection refused
Jun 28 14:03:24 kerrigan pvestatd[1804]: ipcc_send_rec[2] failed: Connection refused
Jun 28 14:03:24 kerrigan pvestatd[1804]: ipcc_send_rec[3] failed: Connection refused
Jun 28 14:03:24 kerrigan pvestatd[1804]: Unable to load access control list: Connection refused
Jun 28 14:03:24 kerrigan pvestatd[1804]: ipcc_send_rec[1] failed: Connection refused
Jun 28 14:03:24 kerrigan pvestatd[1804]: ipcc_send_rec[2] failed: Connection refused
Jun 28 14:03:24 kerrigan systemd[1]: pvestatd.service: Control process exited, code=exited, status=111/n/a
Jun 28 14:03:24 kerrigan pvestatd[1804]: ipcc_send_rec[3] failed: Connection refused
Jun 28 14:03:24 kerrigan systemd[1]: pvestatd.service: Failed with result 'exit-code'.
Jun 28 14:03:24 kerrigan systemd[1]: Failed to start PVE Status Daemon.

sqlite3 /var/lib/pve-cluster/config.db 'PRAGMA integrity_check'

ok

journalctl -xe

Jun 28 14:05:07 kerrigan pveproxy[1912]: worker 2551 started
Jun 28 14:05:07 kerrigan pveproxy[1912]: worker 2552 started
Jun 28 14:05:07 kerrigan pveproxy[1912]: worker 2553 started
Jun 28 14:05:07 kerrigan pveproxy[2551]: /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 1904.
Jun 28 14:05:07 kerrigan pveproxy[2552]: /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 1904.
Jun 28 14:05:07 kerrigan pveproxy[2553]: /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 1904.
Jun 28 14:05:12 kerrigan pveproxy[2551]: worker exit
Jun 28 14:05:12 kerrigan pveproxy[2552]: worker exit
Jun 28 14:05:12 kerrigan pveproxy[2553]: worker exit
Jun 28 14:05:12 kerrigan pveproxy[1912]: worker 2551 finished
Jun 28 14:05:12 kerrigan pveproxy[1912]: worker 2553 finished
Jun 28 14:05:12 kerrigan pveproxy[1912]: worker 2552 finished

 

[Miss Fatale]

I also forgot to mention that I had a power outage a day later, so I was wondering if this could be the reason my config.db is broken.