Big problems after upgrade to 1.5 - can not launch or migrate VPSs

jarcher

Member
Mar 15, 2009
53
1
6
Hi All...

I had a two server cluster running Proxmox 1.3 and today I decided to upgrade to 1.5 with the 2.6.32 kernel. I first migrated my VPSs from the master to the node, so there were no VPSs on it. I followed the instructions in the wiki and did the upgrade. The kernel on the master and the one node is now:

actual02:~# uname -a
Linux actual02 2.6.32-2-pve #1 SMP Thu Apr 15 10:22:46 CEST 2010 x86_64 GNU/Linux

ALso:

actual02:~# pveversion -v
pve-manager: 1.5-9 (pve-manager/1.5/4728)
running kernel: 2.6.32-2-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.32-2-pve: 2.6.32-7
pve-kernel-2.6.24-7-pve: 2.6.24-11
pve-kernel-2.6.24-5-pve: 2.6.24-6
pve-kernel-2.6.24-2-pve: 2.6.24-5
qemu-server: 1.1-14
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
ksm-control-daemon: 1.0-3


I then tried to migrate from the 1.3 node to the 1.5 master, but that failed. I assumed the issue was the mis-match, so I stopped all the VPSs on the node and upgraded it.

proxmox01:~# uname -a
Linux proxmox01 2.6.32-2-pve #1 SMP Thu Apr 15 10:22:46 CEST 2010 x86_64 GNU/Linux

proxmox01:~# pveversion -v
pve-manager: 1.5-9 (pve-manager/1.5/4728)
running kernel: 2.6.32-2-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.32-2-pve: 2.6.32-7
pve-kernel-2.6.24-7-pve: 2.6.24-11
pve-kernel-2.6.18-2-pve: 2.6.18-5
pve-kernel-2.6.24-5-pve: 2.6.24-6
pve-kernel-2.6.24-2-pve: 2.6.24-5
qemu-server: 1.1-14
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
ksm-control-daemon: 1.0-3

Now, I can start only 1 of the 5 VPSs. Here is what the log says when I try to start one:

/usr/bin/ssh -t -t -n -o BatchMode=yes 72.46.65.100 /usr/sbin/vzctl start 101
Unable to open /dev/vzctl: No such file or directory
Please check that vzdev kernel module is loaded and you have sufficient permissions to access the file.
Connection to 72.46.65.100 closed.
VM 101 start failed -

Also, I can not migrate from the node to the master. Here is what happens when I try:

/usr/bin/ssh -t -t -n -o BatchMode=yes 72.46.65.100 /usr/sbin/vzmigrate 72.46.65.62 205
OPT:72.46.65.62
Unable to open /proc/vz/veinfo
Unable to open /proc/user_beancounters
Connection to 72.46.65.100 closed.
VM 205 migration failed -

I would really appreciate some help. One of my mail servers and one of my name servers is down. :-(

Thanks!

Jim
 
Thanks very much, I downgrded the kernel to the stable one and that seemed to fix the issues.

Jim
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!