|How to repair a container startup ? [message #42448]
||Mon, 18 April 2011 22:37
Registered: April 2011
Location: Tours, France
My container startup is in interactive mode ... How to answer to it ?
Here is the container log :
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 ]
ng /etc/fstab swaps: [ OK ]
INIT: Entering runlevel: 3
Entering interactive startup
Start service iscsid (Y)es/(N)o/(C)ontinue? [Y]
I'd try to start it with --wait, but it do not give the chance to answer to the interactive startup ...
# vzctl start 101 --wait
File resolv.conf was modified
Setting quota ugidlimit: 0
Container start in progress, waiting ...
I try "vzctl enter 101" but it does not work :
# vzctl enter 101
enter into CT 101 failed
Unable to open pty: No such file or directory
Have you got an idea ? Should the only solution is to destroy the VM ?