Help! I messed up my PVE by changing the hostname.

[Handryck]

Hi.
I was trying to change the hostname, by editing /etc/hostname and /etc/hosts following the guide from the wiki.
It didn't work as I found 2 different nodes into the Web UI, then I moved all the content from the old node folder in /etc/pve/nodes to the new one (this includes lxc, qemu-server, config and other folders)
I restarted the node and I suddenly got my /etc/pve erased.

Here's the output of journalctl -u pve-cluster

dic 12 13:33:59 proxmox systemd[1]: Starting The Proxmox VE cluster filesystem...
dic 12 13:34:00 proxmox pmxcfs[838]: [database] crit: found entry with duplicate name (inode = 000000000065A5E1, parent = 000000000065A390, name = 'qemu-server')
dic 12 13:34:00 proxmox pmxcfs[838]: [database] crit: found entry with duplicate name (inode = 000000000065A5E1, parent = 000000000065A390, name = 'qemu-server')
dic 12 13:34:00 proxmox pmxcfs[838]: [database] crit: DB load failed
dic 12 13:34:00 proxmox pmxcfs[838]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
dic 12 13:34:00 proxmox pmxcfs[838]: [main] notice: exit proxmox configuration filesystem (-1)
dic 12 13:34:00 proxmox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
dic 12 13:34:00 proxmox pmxcfs[838]: [database] crit: DB load failed
dic 12 13:34:00 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
dic 12 13:34:00 proxmox pmxcfs[838]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
dic 12 13:34:00 proxmox systemd[1]: Failed to start The Proxmox VE cluster filesystem.
dic 12 13:34:00 proxmox pmxcfs[838]: [main] notice: exit proxmox configuration filesystem (-1)
dic 12 13:34:00 proxmox systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
dic 12 13:34:00 proxmox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.
dic 12 13:34:00 proxmox systemd[1]: Stopped The Proxmox VE cluster filesystem.
dic 12 13:34:00 proxmox systemd[1]: Starting The Proxmox VE cluster filesystem...
dic 12 13:34:00 proxmox pmxcfs[881]: [database] crit: found entry with duplicate name (inode = 000000000065A5E1, parent = 000000000065A390, name = 'qemu-server')
dic 12 13:34:00 proxmox pmxcfs[881]: [database] crit: found entry with duplicate name (inode = 000000000065A5E1, parent = 000000000065A390, name = 'qemu-server')
dic 12 13:34:00 proxmox pmxcfs[881]: [database] crit: DB load failed
dic 12 13:34:00 proxmox pmxcfs[881]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
dic 12 13:34:00 proxmox pmxcfs[881]: [main] notice: exit proxmox configuration filesystem (-1)
dic 12 13:34:00 proxmox pmxcfs[881]: [database] crit: DB load failed
dic 12 13:34:00 proxmox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
dic 12 13:34:00 proxmox pmxcfs[881]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
dic 12 13:34:00 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
dic 12 13:34:00 proxmox pmxcfs[881]: [main] notice: exit proxmox configuration filesystem (-1)
dic 12 13:34:00 proxmox systemd[1]: Failed to start The Proxmox VE cluster filesystem.
dic 12 13:34:01 proxmox systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
dic 12 13:34:01 proxmox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 2.
dic 12 13:34:01 proxmox systemd[1]: Stopped The Proxmox VE cluster filesystem.
dic 12 13:34:01 proxmox systemd[1]: Starting The Proxmox VE cluster filesystem...
dic 12 13:34:01 proxmox pmxcfs[907]: [database] crit: found entry with duplicate name (inode = 000000000065A5E1, parent = 000000000065A390, name = 'qemu-server')
dic 12 13:34:01 proxmox pmxcfs[907]: [database] crit: found entry with duplicate name (inode = 000000000065A5E1, parent = 000000000065A390, name = 'qemu-server')
dic 12 13:34:01 proxmox pmxcfs[907]: [database] crit: DB load failed
dic 12 13:34:01 proxmox pmxcfs[907]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
dic 12 13:34:01 proxmox pmxcfs[907]: [main] notice: exit proxmox configuration filesystem (-1)
dic 12 13:34:01 proxmox pmxcfs[907]: [database] crit: DB load failed
dic 12 13:34:01 proxmox pmxcfs[907]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
dic 12 13:34:01 proxmox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
dic 12 13:34:01 proxmox pmxcfs[907]: [main] notice: exit proxmox configuration filesystem (-1)
dic 12 13:34:01 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
dic 12 13:34:01 proxmox systemd[1]: Failed to start The Proxmox VE cluster filesystem.
dic 12 13:34:01 proxmox systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
dic 12 13:34:01 proxmox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
dic 12 13:34:01 proxmox systemd[1]: Stopped The Proxmox VE cluster filesystem.
dic 12 13:34:01 proxmox systemd[1]: Starting The Proxmox VE cluster filesystem...
dic 12 13:34:01 proxmox pmxcfs[913]: [database] crit: found entry with duplicate name (inode = 000000000065A5E1, parent = 000000000065A390, name = 'qemu-server')
dic 12 13:34:01 proxmox pmxcfs[913]: [database] crit: DB load failed
dic 12 13:34:01 proxmox pmxcfs[913]: [database] crit: found entry with duplicate name (inode = 000000000065A5E1, parent = 000000000065A390, name = 'qemu-server')
dic 12 13:34:01 proxmox pmxcfs[913]: [database] crit: DB load failed
dic 12 13:34:01 proxmox pmxcfs[913]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
dic 12 13:34:01 proxmox pmxcfs[913]: [main] notice: exit proxmox configuration filesystem (-1)
dic 12 13:34:01 proxmox pmxcfs[913]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
dic 12 13:34:01 proxmox pmxcfs[913]: [main] notice: exit proxmox configuration filesystem (-1)
dic 12 13:34:01 proxmox systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
dic 12 13:34:01 proxmox systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
dic 12 13:34:01 proxmox systemd[1]: Failed to start The Proxmox VE cluster filesystem.
dic 12 13:34:01 proxmox systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
dic 12 13:34:01 proxmox systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 4.

 

[Moayad]

Hi,

First, make a backup for config.db file then try to edit it and remove duplicated values.


Hope that helps

 

[Handryck]

Hi,

First, make a backup for config.db file then try to edit it and remove duplicated values.


Hope that helps

Hi. I solved by extracting the VZ images from the disk and reinstalled the node to a new SSD.
But, I lost a .raw image of a CT. Is there any way to recover it if it was deleted?

 

[Moayad]

I lost a .raw image of a CT. Is there any way to recover it if it was deleted?

If you have a backup for the LXC Container you could restore it.

 

[Handryck]

If you have a backup for the LXC Container you could restore it.

Unfortunately, I don't...

 

[Dingusnin]

Made an account to say I just got hit by this exact same bug.

Had just got my network setup the way I wanted it. Multi country, several proxmox and pfsense nodes, the whole shebang. all to be undone by changing a hostname. It has been a very long day indeed.