Hi everybody,Today I have a problem with my proxmox servers.In my test lab, I have 3 proxmox servers in clustering mode. I have migrated 2 VMs between 2 nodes without remember that will include some problems with proxmox ID.So now, when i want to restart the pve-cluster service it show me an error : detected duplicate VMID 100 & detected duplicate VMID 101 ...Anybody know how do i resolve this issue ? thx,superwemba
Duplicate VMID
- Thread starter superwemba
- Start date
I a recent 3.x cluster, you cannot get duplicate ID - what version do you run and how did you migrate?
You can manually rename the folders containing the settings for your VM´s below /etc/pve/... and also rename and adapt the VMID.conf file inside this folder.
You can manually rename the folders containing the settings for your VM´s below /etc/pve/... and also rename and adapt the VMID.conf file inside this folder.
Hi tom, thanks for your answer.
pveversion :
pve-manager/3.2-1/1933730b (running kernel: 2.6.32-27-pve)
how did you migrate ?
First -> My VMs are stored in an iscsi san.Sec -> I have run the 'scp' command to copy my vm.conf (/etc/pve/qemu-server) to an other node...third -> disaster ! /etc/pve no mount with restarting /etc/init.d/pve-cluster !
although i found no solution on the web, i found a solution to resolve this problem :
first -> if you have this problem :
root@proxmox-1:/etc# pmxcfs[status] crit: detected duplicate VMID 100[status] crit: detected duplicate VMID 101[main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'[main] notice: exit proxmox configuration filesystem (-1)
you can load this file : /var/lib/pve-cluster/config.db with sqlite
second -> sqlite> select * from tree where name="101.conf"; where 101.conf is your duplicated VM
63|10|145|3|1395062376|8|101.conf|bootdisk: ide0cores: 1ide0: VM1-disk-storage:vm-101-disk-1,size=5Gide2: local:iso/debian-live-7.4-amd64-standard.iso,media=cdrommemory: 512name: Debian-tmpl-DMZnet0: e1000=36:51:A1:03:A4:73,bridge=vmbr5ostype: l26sockets: 1template: 1
212|74|214|2|1395067577|8|101.conf|bootdisk: ide0cores: 1ide0: VM1-disk-storage:vm-101-disk-1,size=5Gide2: local:iso/debian-live-7.4-amd64-standard.iso,media=cdrommemory: 512name: Debian-tmpl-DMZnet0: e1000=36:51:A1:03:A4:73,bridge=vmbr5ostype: l26sockets: 1template: 1
We can see that we have duplicated vm in the database, so we can remove one of them but before i suggest you to save your file :
sqlite> DELETE from tree where inode="212" or inode=”209”; inode 209 was the second VM.
Now you can restart the pve-cluster service.
Regards,
superwemba
pveversion :
pve-manager/3.2-1/1933730b (running kernel: 2.6.32-27-pve)
how did you migrate ?
First -> My VMs are stored in an iscsi san.Sec -> I have run the 'scp' command to copy my vm.conf (/etc/pve/qemu-server) to an other node...third -> disaster ! /etc/pve no mount with restarting /etc/init.d/pve-cluster !
although i found no solution on the web, i found a solution to resolve this problem :
first -> if you have this problem :
root@proxmox-1:/etc# pmxcfs[status] crit: detected duplicate VMID 100[status] crit: detected duplicate VMID 101[main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'[main] notice: exit proxmox configuration filesystem (-1)
you can load this file : /var/lib/pve-cluster/config.db with sqlite
second -> sqlite> select * from tree where name="101.conf"; where 101.conf is your duplicated VM
63|10|145|3|1395062376|8|101.conf|bootdisk: ide0cores: 1ide0: VM1-disk-storage:vm-101-disk-1,size=5Gide2: local:iso/debian-live-7.4-amd64-standard.iso,media=cdrommemory: 512name: Debian-tmpl-DMZnet0: e1000=36:51:A1:03:A4:73,bridge=vmbr5ostype: l26sockets: 1template: 1
212|74|214|2|1395067577|8|101.conf|bootdisk: ide0cores: 1ide0: VM1-disk-storage:vm-101-disk-1,size=5Gide2: local:iso/debian-live-7.4-amd64-standard.iso,media=cdrommemory: 512name: Debian-tmpl-DMZnet0: e1000=36:51:A1:03:A4:73,bridge=vmbr5ostype: l26sockets: 1template: 1
We can see that we have duplicated vm in the database, so we can remove one of them but before i suggest you to save your file :
sqlite> DELETE from tree where inode="212" or inode=”209”; inode 209 was the second VM.
Now you can restart the pve-cluster service.
Regards,
superwemba
Last edited: