URGENT: After upgrade to 1.9 - unable to enter PIAF CTs

bensig

New Member
Feb 10, 2012
2
0
1
I can enter CTs that contain web servers, mysql, asterisk... but NOT pbx in flash containers.

There are 3 containers that I cannot access via SSH the their IP or vzctl enter VEID... These are all PIAF. One has an important a2billing integration on it.

Can someone please assist me with this?

I have had these systems down for a full day and I cannot afford another day offline.
 
i think anybody able to help you needs more details...
- about the CT. os, version, configuratio, etc,
- about your pve host (result of pveversion, for a start)

and, if you have critical systems, you should always perform a test upgrade on a test system before...

Marco
 
Last edited:
Thanks for the quick reply.

HN is:
uname -r
2.6.32-6-pve

pveversion
pve-manager/1.9/6567

The upgrade happened by mistake... I attempted to remove sendmail and install ssmtp on my HN, that led to pve getting uninstalled and then when I did an apt-get install pve, it upgraded to 1.9.

OS of all 3 CTs which are inaccessible are CentOS (Pbx In A Flash) running asterisk and freepbx.

The configuration for them all is openvz.

I should note that I can connect via SSH, but the prompt never comes up, it just HANGS.
 
sorry, try "pveversion -v"...

also, the output of "cat /etc/vz/conf/<VMID>.conf" where <VMID> is the pve id of your openvz vm eg: "102"
(be careful, omit any sensitive conf data)

i'm not an expert about openvz, but anyoune willing to help will need those outputs

you also could "downgrade" pve to 1.8, i think,
see this post about 1.8 > 1.7, should be similar
http://forum.proxmox.com/threads/6177-How-to-downgrade-from-1-8-to-1-7-remotely

also, see al the changed bits in 1.9 that can lead you or others to understand the problem
http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.9

if anything fails, or no expert answers, and your systems are really critical, consider open a support ticket
http://pve.proxmox.com/wiki/Get_support

Marco
 
PiaF is not compatible with that Kernel, not sure why. Downgrade the Kernel and you should have ssh access again

aptitude install pve-kernel-2.6.32-4-pve
nano /boot/grub/menu.lst and set boot order to the new kernel