Ubuntu VE starts only one process [message #38832] |
Mon, 08 February 2010 09:12 ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
robig1
Messages: 6 Registered: February 2010
|
Junior Member |
|
|
Hello,
I've a Problem with OpenVZ and Ubuntu Karmic Koala. After i had updated the VE to karmic, i was wondering why cron isnt running. Ive tried /etc/init.d/cron start but it fails with that message:
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
So it seems to be a upstart problem, was my 1st thought. But because the ve is in use, ive created a clone of it for experimenting wit that problem. And that seems to be my 1st luck that day. The new VE fails to start properly!
# vzctl start 2094
Starting VE ...
VE is mounted
Adding IP address(es): 192.168.2.94
Setting CPU units: 4290
Configure meminfo: 153949
Set hostname: ve2094
File resolv.conf was modified
VE start in progress...
# vzlist 2094
VEID NPROC STATUS IP_ADDR HOSTNAME
2094 1 running 192.168.2.94 ve2094
It seems to have only One process started! Is there any way to find out whats happening with that VE? vzvtl enter is not possible. (no pty)
btw I'running Ubuntu on a Debian host with vzctl version 3.0.22 and kernel 2.6.26-2-openvz-amd64.
I hope you could help me.
Thanks
Robert
[Updated on: Mon, 08 February 2010 10:21] Report message to a moderator
|
|
|
Re: Ubuntu VE starts only one process [message #38871 is a reply to message #38832] |
Sun, 14 February 2010 07:15 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
nuno
Messages: 43 Registered: January 2010
|
Member |
|
|
The problem is indeed upstart.
You need to mount some directories, usually done by initramfs, and start some things manually.
Maybe this will help:
description "upstart with openvz"
start on startup
task
pre-start script
mount -t proc proc /proc
mount -t devpts devpts /dev/pts
mount -t sysfs sys /sys
mount -t tmpfs varrun /var/run
mount -t tmpfs varlock /var/lock
mkdir -p /var/run/network
cat /proc/mounts > /etc/mtab
end script
script
init 2
ifconfig lo 127.0.0.1
/etc/init.d/networking restart
start rsyslog
end script
Create this file and copy it to (the container) /etc/init/openvz.conf
Both Karmic and Lucid expect a newer kernel version, but most things will work.
Regards,
[Updated on: Mon, 15 February 2010 10:28] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|