[SOLVED] OpenVZ x86_64 CT's hanging on startup

[bstriker]

/Edit: Make sure to download templates from http://download.proxmox.com/appliances/system/ (the editor nuked my formatting) I just upgraded to proxmox 3.1 (non-enterprise) from 3.0 originally when I did the upgrade with "apt-get update && apt-get dist-upgrade" the version was 3.1 but the new "update" tab in the web gui didn't show up. I also noticed my CT's weren't starting up properly. I did some research and noticed the version hash didn't match dc0e9b0e, so I figured maybe a clean install would solve the issue. Using the latest 3.1 iso it installed fine, but the issue still remains. (the "update" tab shows up) I've tried updating packages, commenting out the enterprise repository, had to run "rm -f /var/lib/apt/lists/ftp.us.debian.org*" to be able to install any packages. But the symptom still remains. MY research shows it might be something to do with tty not starting. Watching freshly installed CT's starting they hang on "Init ...... : Cron" right after the ssh rsa key is generated. When connecting to an already mounted CT all i see is black with a "`" int the top left. I also see errors about mounting and such. I'm currently at work, but if screen shots or detailed errors are need please let me know. I'd appreciate any help! Thanks for reading !

root@proxmox:~# pveversion --verbose proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve) pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e) pve-kernel-2.6.32-23-pve: 2.6.32-109 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.5-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.0-1 pve-cluster: 3.0-7 qemu-server: 3.1-1 pve-firmware: 1.0-23 libpve-common-perl: 3.0-6 libpve-access-control: 3.0-6 libpve-storage-perl: 3.0-10 pve-libspice-server1: 0.12.4-1 vncterm: 1.1-4 vzctl: 4.0-1pve3 vzprocps: 2.0.11-2 vzquota: 3.1-2 pve-qemu-kvm: 1.4-17 ksm-control-daemon: 1.1-1 glusterfs-client: 3.4.0-2

 

[Raymond Burns]

Re: OpenVZ x86_64 CT's hanging on startup after Proxmox 3.1 (upgrade / fresh install)

Have you tried to SSH into the Proxmox Server or click Shell when the "Node" is selected and tried

vzctl enter "VMID"

 

[bstriker]

Re: OpenVZ x86_64 CT's hanging on startup after Proxmox 3.1 (upgrade / fresh install)

Have you tried to SSH into the Proxmox Server or click Shell when the "Node" is selected and tried

vzctl enter "VMID"

This is the proxmox console view



the "vzctl enter" worked, here's what top is showing

    1 root      20   0 30176 2112 1408 S   0.0  0.4   0:00.07 init
    2 root      20   0     0    0    0 S   0.0  0.0   0:00.00 kthreadd/999
    3 root      20   0     0    0    0 S   0.0  0.0   0:00.00 khelper/999
   81 root      20   0 16984  876  652 S   0.0  0.2   0:00.00 upstart-udev-br
   87 root      20   0 21296 1320  772 S   0.0  0.3   0:00.01 udevd
  124 root      20   0 21292 1020  464 S   0.0  0.2   0:00.00 udevd
  125 root      20   0 21292 1020  464 S   0.0  0.2   0:00.00 udevd
  202 root      20   0 14932  628  440 S   0.0  0.1   0:00.00 upstart-socket-
 1627 root      20   0 49804 1212  604 S   0.0  0.2   0:00.00 sshd
 1657 root      20   0 58748 1628 1180 S   0.0  0.3   0:00.00 rsyslogd
 1702 root      20   0 57484  988  404 S   0.0  0.2   0:00.00 saslauthd
 1704 root      20   0 57484  632   48 S   0.0  0.1   0:00.00 saslauthd
 1860 root      20   0 55660 2132  604 S   0.0  0.4   0:00.00 sendmail-mta
 1933 root      20   0 19516  952  756 S   0.0  0.2   0:00.00 xinetd
 1966 root      20   0 71572 2960 1308 S   0.0  0.6   0:00.00 apache2
 1969 www-data  20   0 71596 2280  620 S   0.0  0.4   0:00.00 apache2
 2010 root      20   0 18832  968  736 S   0.0  0.2   0:00.00 cron
 2148 root      20   0 25532  692  484 S   0.0  0.1   0:00.00 vzctl
 2149 root      20   0 17804 1976 1508 S   0.0  0.4   0:00.00 bash
 2263 root      20   0 21600 1456 1072 R   0.0  0.3   0:00.00 top

 

[Raymond Burns]

Re: OpenVZ x86_64 CT's hanging on startup after Proxmox 3.1 (upgrade / fresh install)

Great, just verify you are in the CT with uname -x
Once you know you are within the CT filesystem, follow the instructions from http://pve.proxmox.com/wiki/OpenVZ_Console
The reason I say to verify that you have entered the CT filesystem is because you do not want to modify the Proxmox filesystem.
Also, be sure to edit the /etc/init/tty.conf and NOT the /etc/init.d/tty.conf
I did the latter and had to wipe the egg off after multiple reboots.

There is also a way to edit the template creation to include this, but I did not take it that far. I will wait for Proxmox to change the template files.

 

[bstriker]

Re: OpenVZ x86_64 CT's hanging on startup after Proxmox 3.1 (upgrade / fresh install)

Well my tty configs looked fine?

I tried following the this thread just in-case it was the same issue but I'm still stuck on this screen



I'm not a noob with linux, but this sure does feel over my head.

 

[bstriker]

Re: OpenVZ x86_64 CT's hanging on startup after Proxmox 3.1 (upgrade / fresh install)

Wow... apparently I was downloading templates from the wrong source... here's the place to download them if anyone is running into this issue http://download.proxmox.com/appliances/system/