Status mounted after reboot

[mccharlet]

Hi,

I have exécute de roboot command to my VE and my server not restart.
It's possible to restart ?

Thanks and sorry for my english

 

[tom]

Hi,

I have exécute de roboot command to my VE and my server not restart.
It's possible to restart ?

Thanks and sorry for my english

you need to wait several minutes and then the container will start again automatically - this is openvz standard behavior.

 

[mccharlet]

Thanks

 

[anthonysomerset]

is there anyway of reducing this time to say 30 seconds?

 

[dietmar]

you can edit '/etc/vz/cron/vz' - check every minute is possible.

 

[anthonysomerset]

this is perfect thank you

 

[Sorcerer]

Hello,

i have the same Problem with a couple of my VMs.

But only with OpenVZ VMs which I have moved from our former OpenVZ Server to the Proxmox Server.

A VM that I created from a template starts when i execute the script "/usr/share/vzctl/scripts/vpsreboot", but my old VMs are still in the status "mounted".

I created a new conf file for the old VMs, but they were still ignored from the vpsreboot script.

Can you help me with that Problem?

Greetings,

Marcel

 

[tom]

what OS template do have this issue? its know issue for Debian Squeeze, other should work.

 

[Sorcerer]

Hello Tom,

thanks for the fast response.

They are old VMs, Debian Based, must be Etch based at that time.

 

[tom]

these should work (5 minutes). did you followed this guide?

 

[Sorcerer]

Hi Tom,

not exactly that way. The old openVZ Server had an Hardware Error and i used the Backup of the VZs from the last night that were made with vzdump.

I restored the VZs with vzdump on the ProxMox Server and edit the conf File.

What can I make to solve the Problem with the Status mounted by a reboot?

 

[Sorcerer]

At the weekend i have updateted my ProxMox Servers to Version 1.7 with the kernel 2.6.32.

But the Problem still occurs with my openvz vms from my the old Server.

Is there a workaround to fix this Problem?

 

[Petrus4]

you need to wait several minutes and then the container will start again automatically - this is openvz standard behavior.

Hi Tom, why is this standard behaviour? Is there any way to bypass it with a command?

 

[tom]

latest vzctl versions supports vzeventd to handle CT shutdown/reboot - its not available yet for Proxmox VE but its on the todo list.

 

[peter_700]

Hello Tom,

what OS template do have this issue? its know issue for Debian Squeeze, other should work.

is a issue to fix this?

regards,
Peter

 

[naja7host]

Same error here .

the VM template is not debian , is centos_64 . the cronjob vpsreboot not giving anyerror , and none of my vps are rebooted . i have tested in all my vps and not working !!! where should i go to diagnostic ?

pveversion -v
pve-manager: 1.7-11 (pve-manager/1.7/5470)
running kernel: 2.6.24-11-pve
proxmox-ve-2.6.24: 1.5-23
pve-kernel-2.6.24-11-pve: 2.6.24-23
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1
pve-qemu-kvm: 0.13.0-3

i have found that the ALLOWREBOOT=”yes” is not set in the conf file ve .o have added manaully but no result , i have missed something ?

 

[naja7host]

After i add the ALLOWREBOOT=”yes” to the conf ve file , and restarted the vm and reboot from inside the vm , it work now like a charm .

it should add this line to the default ve config file .

 

[Sorcerer]

i have add ALLOWREBOOT=”yes” to the config files, but it doesn´t work.

Is there a fix to fit this failure?

Or when is vzeventd avaible in proxmox?

 

[tom]

...
Or when is vzeventd avaible in proxmox?

As far as these features are available in a stable version (stable OpenVZ for 2.6.32) we will test them.