pve-cluster service wont start

chrkov

New Member
May 23, 2024
2
0
1
Rebooted server today and I am getting most of the services failing to start.

I know most things are not going to work if pve-cluster doesn't start, which its not.

I am seeing the following in the log

Feb 12 10:56:34 wlpt-prmx-s01 pmxcfs[4644]: [main] notice: resolved node name 'wlpt-prmx-s01' to '192.168.41.40' for default node IP address
Feb 12 10:56:34 wlpt-prmx-s01 pmxcfs[4644]: [main] notice: resolved node name 'wlpt-prmx-s01' to '192.168.41.40' for default node IP address
Feb 12 10:56:34 wlpt-prmx-s01 pmxcfs[4644]: [database] crit: found entry with duplicate name 'qemu-server' - A:(inode = 0x000000000005D510, parent = 0x000000000005D4DE, v./mtime = 0x5D510/0x1739277449) vs. B:(inode = 0x00000000000>
Feb 12 10:56:34 wlpt-prmx-s01 pmxcfs[4644]: [database] crit: found entry with duplicate name 'qemu-server' - A:(inode = 0x000000000005D510, parent = 0x000000000005D4DE, v./mtime = 0x5D510/0x1739277449) vs. B:(inode = 0x00000000000>
Feb 12 10:56:34 wlpt-prmx-s01 pmxcfs[4644]: [database] crit: DB load failed
Feb 12 10:56:34 wlpt-prmx-s01 pmxcfs[4644]: [database] crit: DB load failed
Feb 12 10:56:34 wlpt-prmx-s01 pmxcfs[4644]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Feb 12 10:56:34 wlpt-prmx-s01 pmxcfs[4644]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Feb 12 10:56:34 wlpt-prmx-s01 pmxcfs[4644]: [main] notice: exit proxmox configuration filesystem (-1)
Feb 12 10:56:34 wlpt-prmx-s01 pmxcfs[4644]: [main] notice: exit proxmox configuration filesystem (-1)
Feb 12 10:56:34 wlpt-prmx-s01 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION


Looks like I have some duplicate entry and not sure how to correct it.

Any help is appreciated.
 
Have you changed the host's name?
What's in your /etc/hostname and /etc/hosts ?
Yes, I did.

I found the following topic that corrected my issue also.

 
Yes, I did.
Would be nice if you provided that little detail ;)

For reference, there is a long thread regarding host name change with different procedures, some for older versions [1]

You probably had some configurations in the host too. Some combinations of changes end up with a database error like the one you had. For the record: did you manually moved anything within /etc/pve? Was it before or after restarting with the new hostname? Thanks!

[1] https://forum.proxmox.com/threads/proxmox-node-name-change.14327/