Unable to mount filesystem after trying to change hostname

ATX

New Member
Nov 5, 2019
20
0
1
37
Code:
-- Subject: A start job for unit pve-cluster.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-cluster.service has begun execution.
--
-- The job identifier is 53830.
Aug 30 11:01:41 proxmox6 pmxcfs[7363]: [database] crit: found entry with duplicate name (inode = 0000000000F86360, parent = 0000000000F862E5, name = 'qemu-server')
Aug 30 11:01:41 proxmox6 pmxcfs[7363]: [database] crit: found entry with duplicate name (inode = 0000000000F86360, parent = 0000000000F862E5, name = 'qemu-server')
Aug 30 11:01:41 proxmox6 pmxcfs[7363]: [database] crit: DB load failed
Aug 30 11:01:41 proxmox6 pmxcfs[7363]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Aug 30 11:01:41 proxmox6 pmxcfs[7363]: [main] notice: exit proxmox configuration filesystem (-1)
Aug 30 11:01:41 proxmox6 pmxcfs[7363]: [database] crit: DB load failed
Aug 30 11:01:41 proxmox6 pmxcfs[7363]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Aug 30 11:01:41 proxmox6 pmxcfs[7363]: [main] notice: exit proxmox configuration filesystem (-1)
Aug 30 11:01:41 proxmox6 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
 
SOLVED
For traceability: I had to remove duplicated values from '/var/lib/pve-cluster/config.db'.

CONCLUSION
CHANGING HOSTNAMES SEEMS REALLY DANGEROUS AND MANY OTHER POSTS HAVE THE SAME ISSUE