OpenVZ Forum: Support » not starting on boot (onboot="yes" in conf files)

Home » General » Support » not starting on boot (onboot="yes" in conf files)

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

not starting on boot (onboot="yes" in conf files) [message #43100]

Thu, 21 July 2011 15:31

vmvmvm
Messages: 51
Registered: January 2006

Member

Hi,

I have a particular hardware node that has stopped booting ve's on reboot.

All the ve's have :

onboot="yes"

set

The server does start the openvz service via /etc/rc.d/init.d as far as I can tell.

If I reboot the node, vzlist shows something similar to "no containers found" (I don't recall the exact wording).

If I start them manually everything works fine.

Any ideas? Thanks in advance.

Report message to a moderator

Re: not starting on boot (onboot="yes" in conf files) [message #43101 is a reply to message #43100]

Thu, 21 July 2011 15:35

kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia

Senior Member

AFAIK the word "ONBOOT" should be in UPPERCASE, maybe that's your problem. From http://wiki.openvz.org/Man/ctid.conf.5:

All parameter names and values are case-sensitive.

Kir Kolyshkin

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: not starting on boot (onboot="yes" in conf files) [message #43102 is a reply to message #43101]

Thu, 21 July 2011 15:40

kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia

Senior Member

Actually, any vzctl command (except for status) with --verbose flag set should complain like this:

# vzctl --verbose mount $CTID
Warning at /etc/vz/conf/106.conf:18: unknown parameter onboot ("yes"), ignored

Kir Kolyshkin

[Updated on: Thu, 21 July 2011 15:42]

Report message to a moderator

Re: not starting on boot (onboot="yes" in conf files) [message #43103 is a reply to message #43102]

Thu, 21 July 2011 15:42

kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia

Senior Member

Same for vzlist, it doesn't recognize lowercased variable (which is correct thing to do):

dionysos ~ # grep -i onboot /etc/vz/conf/106.conf 
onboot="yes"

dionysos ~ #  vzlist -o ctid,onboot 106
      CTID ONBOOT
       106     no

Kir Kolyshkin

Report message to a moderator

Re: not starting on boot (onboot="yes" in conf files) [message #43108 is a reply to message #43103]

Thu, 21 July 2011 16:55

vmvmvm
Messages: 51
Registered: January 2006

Member

Hi,

Thanks for your help. I mistyped in the subject line. In the actual conf file they are correctly in caps:

ONBOOT="yes"

# UBC parameters (in form of barrier:limit)
KMEMSIZE="15252512:15252512"

etc...

I've not been able to test it yet but the last change I see is
changing VZFASTBOOT to yes on this server:

DISK_QUOTA=yes
VZFASTBOOT=yes

(it was set to no)

I do not think this is the problem because we have it set to YES on other servers with no problem. I've not been able to test yet (can't reboot as this is a production machine) but it should have not be stopping automatic starts of the VE's from my undestanding.

To manually start, I've been doing this:

for VE in `vzlist -SHoveid`; do echo $VE; vzctl start $VE; done

Report message to a moderator

Re: not starting on boot (onboot="yes" in conf files) [message #43109 is a reply to message #43108]

Thu, 21 July 2011 17:12

vmvmvm
Messages: 51
Registered: January 2006

Member

I believe I may have found the cause of this.

/vz/private is on a different drive, with a symlink from /vz/private to the drive:

private -> /mnt/drive2/vz/private

I wonder if the drive is mounted after vz attempts to start it fails? I cannot find anything in the logs indicating a failure but I wonder if this may be the case?

The drive was an emergency change and not added to fstab

The drive is instead mounted in rc.local (likely after vz has tried to start)

Does this sound like the cause? Should this give an error someplace when vz tries to start containers with missing private directories? I'd like to find it in the logs so I can be 100% sure this is the cause.

Thanks again.

[Updated on: Thu, 21 July 2011 17:18]

Report message to a moderator

Previous Topic:	Container internet access using wifi
Next Topic:	openvz hangs on hp blade running centos 5.6

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Apr 30 08:13:35 GMT 2024

Total time taken to generate the page: 0.01573 seconds