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.
|
|
|
|
|
|
|
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
|
|
|