Hi,
I had installed manually proxmox 3.1 into debian wheezy and it was working great with a few VMs on.
Yesterday I tried to enable HA since now I have two machines. I have put the new machine (installed with debian wheezy, then proxmox 3.1 and then upgraded to 3.3 flawlessly) as master and then when I tried to put my old machine as slave, all went foobar.
1. I couldn't add the slave successfully as it kept stuck on "Waiting for quorum"
2. I lost all the VM configurations on the slave, but they are still running and /var/lib/vz is intact
So as everything went wrong, I decided to try to disable HA on the slave to keep it running as before. I followed these steps: http://undefinederror.org/how-to-reset-cluster-configuration-in-proxmox-2/ and omitted the part of creating a cluster.
After It didn't work, I decided to upgrade from 3.1 to 3.3 expecting to clean things up.
apt-get dist-upgrade shows the following output:
Proxmox webpage is not working anymore (doesn't load anything even after restarting the services). Pveproxy shows
maybe because an inconsistent upgrade.
pveversion -v
Any suggestion on how to repair the installation? On the other side, at my new machine I have a clean proxmox 3.3 installation with a cluster created, maybe it can help with some files.
Thanks and merry christmas!
I had installed manually proxmox 3.1 into debian wheezy and it was working great with a few VMs on.
Yesterday I tried to enable HA since now I have two machines. I have put the new machine (installed with debian wheezy, then proxmox 3.1 and then upgraded to 3.3 flawlessly) as master and then when I tried to put my old machine as slave, all went foobar.
1. I couldn't add the slave successfully as it kept stuck on "Waiting for quorum"
2. I lost all the VM configurations on the slave, but they are still running and /var/lib/vz is intact
So as everything went wrong, I decided to try to disable HA on the slave to keep it running as before. I followed these steps: http://undefinederror.org/how-to-reset-cluster-configuration-in-proxmox-2/ and omitted the part of creating a cluster.
After It didn't work, I decided to upgrade from 3.1 to 3.3 expecting to clean things up.
apt-get dist-upgrade shows the following output:
Code:
root@helix:/var/log# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
pve-qemu-kvm qemu-server
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? Y
Setting up pve-manager (3.3-1) ...
insserv: Service cman has to be enabled to start service pvedaemon
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up vzctl (4.0-1pve6) ...
insserv: Service cman has to be enabled to start service vz
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing vzctl (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
proxmox-ve-2.6.32 depends on pve-manager; however:
Package pve-manager is not configured yet.
proxmox-ve-2.6.32 depends on vzctl (>= 3.0.29); however:
Package vzctl is not configured yet.
dpkg: error processing proxmox-ve-2.6.32 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
vzctl
proxmox-ve-2.6.32
E: Sub-process /usr/bin/dpkg returned an error code (1)
Proxmox webpage is not working anymore (doesn't load anything even after restarting the services). Pveproxy shows
Code:
Dec 23 23:57:30 helix pveproxy[387691]: WARNING: Can't call method "timeout_reset" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 225.
pveversion -v
Code:
pveversion -v
proxmox-ve-2.6.32: not correctly installed (running kernel: 2.6.32-26-pve)
pve-manager: not correctly installed (running version: 3.3-1/a06c9f73)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.1-8
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: not correctly installed
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
Any suggestion on how to repair the installation? On the other side, at my new machine I have a clean proxmox 3.3 installation with a cluster created, maybe it can help with some files.
Thanks and merry christmas!