I recently set up a server to test (48 cores, 32G ram, ZFS). It has been running 8.0.2 originally, and updated to 8.0.4 a week ago. I did not do a reboot of it till last night and didn't know it was updated. In my scenario, I set up a second node. I created a cluster on PVE, did pve version and noticed 8.04, so I did updates on the second node and, then tried to attach. It failed with a cert error:
'/etc/pve/nodes/pve2/pve-ssl.pem' does not exist! (500)
I didn't think anything of the vm that was already running on the first PVE. It was Server 2012,
12G Ram, 8 cores, Seahorse, Default display, PC-I440FX-8.0, VirtIO SCSI controller, Sata drive on ZFS, e1000 network.
When the join failed, I had to delnode 2 and then rebooted.
After rebooting, the Windows 2012 Server install will no longer successfully boot. It gets to the spinning circle, ram starts to climb, then the circle freezes and statuses stop updating properly. Then the vnc fails. I tried rebooting it again, tried to get to safe mode, checked the logs and this is all I found:
VM 100 qmp command failed - VM 100 qmp command 'query-proxmox-support' failed - unable to connect to VM 100 qmp socket - timeout after 51 retries
After, I questioned if the update may have brought out a hardware incompatibility with my server, it is quite new, so I tried to back it up (stopped) using the gui, so I could load it on another and test other hardware. It was 1tb and took about 4 hours to get to 99%, then stayed there for the next 5 hours. I have tried twice in the GUI with failure. I am running it from the command line now to see and have about 30 minutes left.
***Update*** The backup succeeded from the CLI.
Any information would be very helpful.
Could creating a cluster cause the problem? Update error? Hardware incompatible?
Thank you.
'/etc/pve/nodes/pve2/pve-ssl.pem' does not exist! (500)
I didn't think anything of the vm that was already running on the first PVE. It was Server 2012,
12G Ram, 8 cores, Seahorse, Default display, PC-I440FX-8.0, VirtIO SCSI controller, Sata drive on ZFS, e1000 network.
When the join failed, I had to delnode 2 and then rebooted.
After rebooting, the Windows 2012 Server install will no longer successfully boot. It gets to the spinning circle, ram starts to climb, then the circle freezes and statuses stop updating properly. Then the vnc fails. I tried rebooting it again, tried to get to safe mode, checked the logs and this is all I found:
VM 100 qmp command failed - VM 100 qmp command 'query-proxmox-support' failed - unable to connect to VM 100 qmp socket - timeout after 51 retries
After, I questioned if the update may have brought out a hardware incompatibility with my server, it is quite new, so I tried to back it up (stopped) using the gui, so I could load it on another and test other hardware. It was 1tb and took about 4 hours to get to 99%, then stayed there for the next 5 hours. I have tried twice in the GUI with failure. I am running it from the command line now to see and have about 30 minutes left.
***Update*** The backup succeeded from the CLI.
Any information would be very helpful.
Could creating a cluster cause the problem? Update error? Hardware incompatible?
Thank you.
Last edited: