[Users] Starting CentOS 5.x container... never fully init's

[Tim Nelson]

----- "Dietmar Maurer" <dietmar at proxmox.com> wrote:
> > virtbox1:~# vzctl enter 103
> > entered into CT 103
> > [root at pxebox /]# ps aux
> > USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME
> COMMAND
> > root         1  0.0  0.0   2068   612 ?        Ss   20:42   0:00
> init [3]
> > root        21  0.0  0.0    100    16 ?        S    20:42   0:00
> [init-logger]
> 
> You run init logger - so what is the content of /var/log/init.log  -
> any hint there?
> 

Greetings Dietmar-


I didn't even think to look at the init log!


Here are the contents:


[root at pxebox log]# cat init.log
starting init logger
INIT: version 2.86 booting
/etc/rc.d/rc.sysinit: line 240: /dev/tty1: Operation not permitted
                Welcome to  CentOS release 5.4 (Final)
                Press 'I' to enter interactive startup.
hwclock is unable to get I/O port access:  the iopl(3) call failed.
Setting clock  (localtime): Thu Nov 18 20:48:01 CST 2010 [  OK  ]
Loading default keymap (us): /etc/rc.d/rc.sysinit: line 396: /dev/tty0: Operation not permitted
[FAILED]
Setting hostname pxebox.internal:  [  OK  ]
raidautorun: failed to open /dev/md0: Operation not permitted
awk: cmd. line:1: fatal: cannot open file `/proc/misc' for reading (No such file or directory)
Mounting local filesystems:  [  OK  ]
Enabling local filesystem quotas:  [  OK  ]
/etc/rc.d/rc.sysinit: line 793: /dev/urandom: Operation not permitted
ng /etc/fstab swaps:  [  OK  ]
INIT: Entering runlevel: 3
Entering interactive startup
Start service microcode_ctl (Y)es/(N)o/(C)ontinue? [Y] 


So, it looks like the 'rc 3' is hanging because it's expecting interactive startup? How do I force rc to run in non-interactive mode?

Thank you!!

--Tim