Init Problem on Ubuntu Gutsy Gibson [message #22225] |
Tue, 23 October 2007 19:06  |
ckpeter
Messages: 8 Registered: October 2006
|
Junior Member |
|
|
I am working on a gutsy 7.10 template cache for OpenVZ.
The way I have done so is by using the available dapper 6.06 template as a base, and progressively upgrade to edgy, then feisty, and gutsy.
I now have the template built out, but I am having trouble with init. It seems like the init daemon is stuck on something and is consuming 100% CPU. I am able to enter the VE by vzctl enter, and I can even install packages and perform other tasks, but no service is started up and runlevel says it is unknown.
The host OS is CentOS 5.
uname -a:
2.6.18-8.1.8.el5.028stab039.1 #1 SMP Mon Jul 23 18:02:32 MSD 2007 x86_64 x86_64 x86_64 GNU/Linux
rpm -q vzctl:
vzctl-3.0.18-1
Any idea why init is stuck on 100% CPU usage? I read about problems with OpenVZ and the upstart implementation in prior version of ubuntu, but I assume that that has already been fixed.
[Updated on: Fri, 26 October 2007 18:33] Report message to a moderator
|
|
|
|
Re: Ubuntu Gutsy Gibson Template Cache [message #22304 is a reply to message #22225] |
Wed, 24 October 2007 16:06   |
ckpeter
Messages: 8 Registered: October 2006
|
Junior Member |
|
|
I ran a strace:
[root@host ~]# strace -fF -o vz.out vzctl --verbose start 3001
Starting VE ...
VE is mounted
Adding IP address(es): x.x.x.x
Running VE script: /etc/vz/dists/scripts/debian-add_ip.sh
[ Process PID=18853 runs in 32 bit mode. ]
[ Process PID=18852 runs in 64 bit mode. ]
Execution timeout expired
ptrace: umoven: Input/output error
Got signal 15
Setting CPU units: 1000
Configure meminfo: 204800
Running VE script: /etc/vz/dists/scripts/set_dns.sh
[ Process PID=19118 runs in 32 bit mode. ]
[ Process PID=19117 runs in 64 bit mode. ]
[ Process PID=19118 runs in 32 bit mode. ]
[ Process PID=19117 runs in 64 bit mode. ]
[ Process PID=19118 runs in 32 bit mode. ]
[ Process PID=19117 runs in 64 bit mode. ]
Execution timeout expired
ptrace: umoven: Input/output error
Got signal 15
File resolv.conf was modified
VE start in progress...
[ Process PID=18826 runs in 32 bit mode. ]
At this point I control-C to get out of the process.
The trace file reveals that it is choking on /dev/console:
18826 open("/dev/console", O_WRONLY|O_NOCTTY) = -1 EACCES (Permission denied)
18826 read(3, 0xbff6f20b, 1) = -1 EAGAIN (Resource temporarily unavailable)
18826 waitid(P_ALL, 0, {}, WNOHANG|WEXITED|WNOWAIT, NULL) = 0
18826 time(NULL) = 1193241775
18826 select(4, [0 3], [], [], NULL) = 1 (in [0])
18826 getsockname(0, 0xbff6ef04, [112]) = -1 ENOTSOCK (Socket operation on non-socket)
18826 recvmsg(0, 0xbff6efa8, MSG_PEEK) = -1 ENOTSOCK (Socket operation on non-socket)
18826 time(NULL) = 1193241775
18826 stat64(0xb7fb83a6, 0xbff6ebe8) = 0
18826 stat64(0xb7fb83a6, 0xbff6eaa0) = 0
18826 stat64(0xb7fb83a6, 0xbff6eaa0) = 0
18826 socket(PF_FILE, SOCK_DGRAM, 0) = 1
18826 fcntl64(1, F_SETFD, FD_CLOEXEC) = 0
18826 connect(1, {sa_family=AF_FILE, path="/dev/log"}, 110) = -1 ENOENT (No such file or directory)
18826 close(1) = 0
18826 open("/dev/console", O_WRONLY|O_NOCTTY) = -1 EACCES (Permission denied)
18826 read(3, 0xbff6f20b, 1) = -1 EAGAIN
The preceding output repeats over and over.
[Updated on: Fri, 26 October 2007 18:31] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|