OpenVZ Forum: Support » How to repair a container startup ?

Home » General » Support » How to repair a container startup ? (My container startup is in interactive startup mode ... How to answer to it ?)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

How to repair a container startup ? [message #42448]

Tue, 19 April 2011 02:37

Cyrille37
Messages: 6
Registered: April 2011
Location: Tours, France

Junior Member

Hi,

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 ?

Regards
Cyrille

Report message to a moderator

Re: How to repair a container startup ? [message #42498 is a reply to message #42448]

Fri, 22 April 2011 18:05

curtis_isparks
Messages: 14
Registered: April 2011

Junior Member

I don't know if this is what you are looking for, but you can disable the interactive prompts (so that your container will boot) by editing /etc/sysconfig/init and switching the PROMPT setting to no...

PROMPT=no

Hope this helps. Smile

Report message to a moderator

Re: How to repair a container startup ? [message #42511 is a reply to message #42448]

Mon, 25 April 2011 13:12

Cyrille37
Messages: 6
Registered: April 2011
Location: Tours, France

Junior Member

Hi
and thanks for your answer.

The fact is that I didn't see that I can easily access to the container file-system to apply your trick and other configuration. I was afraid that VMs are contained in a obscure file like with VirtualBox.

Thanks
Cyrille

Report message to a moderator

Previous Topic:	Load spikes issue
Next Topic:	ssh log prob

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Apr 13 13:58:58 GMT 2026

Total time taken to generate the page: 0.34070 seconds