openVZ container /proc empty?

J

Jeffrey

New Member
Mar 10, 2010
13
0
1
I am in the process in playing around with Proxmox v1.5

I created a openVz container from a debian-6.0-standard_6.0-1 template.
Had it running, did a apt-get update and such, installed openssh and had everything working. I assigned a static IP address and was playing around with a dhcp/ddns server on this container.

I shutdown the container last night, started it back up today and when I tired to start it up I ran into some troubles.

I opened a VNC console and was met with an error:

"Unable to get tty name: Bad file descriptor"

I was poking around and noticed that /proc was empty...

This has happened to two containers so far, I have other containers that are working without problems.

Any ideas? Solutions?

Thanks,
Jeffrey
 
I've had this really bad surprise myself today. Fortunately in IRC helped me, and the solution is trivial:
In the container edit: /etc/default/rcS
and add:
CONCURRENCY=none
Seems that there is a problem with the upgraded init-scripts package which defaults to do concurrency which seems to fail.
In chat I've been told that this solution does not work with ubuntu 10.04 though (and no solution has been suggested).
Hope it helps :)
 
just to mention, we already have version 6.0-2 since a week - can you test if this works better for you?
 
Installed 6.0-2 and aptitude update / full-upgrade, seems to work fine, thanks.
Any way to "fix" previous installations except the "CONCURRENCY=none" trick? I've no idea what are the implication of this parameter, nor if is safe for future upgrades.
An additional question... will ubuntu 10.04 LST templates be available soon?
Thanks
 
mmenaz said:
I've had this really bad surprise myself today. Fortunately in IRC helped me, and the solution is trivial:
In the container edit: /etc/default/rcS
and add:
CONCURRENCY=none
Seems that there is a problem with the upgraded init-scripts package which defaults to do concurrency which seems to fail.
In chat I've been told that this solution does not work with ubuntu 10.04 though (and no solution has been suggested).
Hope it helps :)
Click to expand...

To update and close this thread...

Yes, it did work.!
After it was working again, I updated/dist-upgraded and restart the container a few times and it seems to still be working!

Many thanks.
 
You must log in or register to reply here.
Top Bottom