OpenVZ Forum


Home » General » Support » not starting on boot (onboot="yes" in conf files)
Re: not starting on boot (onboot="yes" in conf files) [message #43109 is a reply to message #43108] Thu, 21 July 2011 17:12 Go to previous message
vmvmvm is currently offline  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

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


Current Time: Fri Sep 27 23:33:19 GMT 2024

Total time taken to generate the page: 0.04294 seconds