[Users] VE fails to stop

2007-12-10 Thread Cliff Wells
Hardware: dual Opteron 242 Kernel: linux-2.6.18-openvz-028.049 Host OS: Gentoo Guest OS: ubuntu-7.10-i386-minimal Both host and VE are fresh installs. I noticed that "vzctl stop 101" would fail with Stopping VPS ... Unable to stop VPS, operation timed out This of course also prevented me from

Re: [Users] VE fails to stop

2007-12-10 Thread Cliff Wells
On Mon, 2007-12-10 at 17:20 -0800, Cliff Wells wrote: > Guest OS: ubuntu-7.10-i386-minimal > > Does this appear to be a problem with OVZ or with the guest template? > Answering my own question: it appears that the template is broken. centos-5-i386-minimal works fine. Cliff _

Re: [Users] VE fails to stop

2007-12-11 Thread Kirill Korotaev
Ubuntu 7.10 requires the latest vzctl (check http://git.openvz.org to compile it) otherwise init does busy loop on VE start (plz check it), so it can hang and not stop. (`kill -KILL Hardware: dual Opteron 242 > Kernel: linux-2.6.18-openvz-028.049 > Host OS: Gentoo > Guest OS: ubuntu-7.10-i386-min

Re: [Users] VE fails to stop

2007-12-11 Thread Kir Kolyshkin
This is probably a problem with VE start, not stop. VE started badly and can not stop. This is known issue (a bad interaction of Ubuntu's upstart (init replacement) and vzctl) which is fixed in upcoming vzctl release, see http://bugzilla.openvz.org/662 Now you have three options: 1. Wait for

Re: [Users] VE fails to stop

2007-12-11 Thread Cliff Wells
On Tue, 2007-12-11 at 19:35 +0300, Kir Kolyshkin wrote: > This is probably a problem with VE start, not stop. VE started badly and > can not stop. > > This is known issue (a bad interaction of Ubuntu's upstart (init > replacement) and vzctl) which is fixed in upcoming vzctl release, see > http:

Re: [Users] VE fails to stop

2007-12-11 Thread Cliff Wells
On Tue, 2007-12-11 at 23:10 -0800, Cliff Wells wrote: > > Could this be another problem with upstart? Apparently not. Switching to sysvinit didn't have any effect. Cliff ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/us

Re: [Users] VE fails to stop

2007-12-12 Thread Kir Kolyshkin
Cliff Wells wrote: On Tue, 2007-12-11 at 19:35 +0300, Kir Kolyshkin wrote: This is probably a problem with VE start, not stop. VE started badly and can not stop. This is known issue (a bad interaction of Ubuntu's upstart (init replacement) and vzctl) which is fixed in upcoming vzctl releas

Re: [Users] VE fails to stop

2007-12-13 Thread Kir Kolyshkin
OK, here's what I found concerning ubuntu-7.10 VE vs. OpenVZ. 0. (just repeating) Ubuntu-7.10 template with upstart instead of init requires vzctl > 3.0.18. An updated vzctl (apparently it will have version of 3.0.21) is not yet released. 1. There was an obscure bug in not-yet-released vzctl,

Re: [Users] VE fails to stop

2007-12-13 Thread Cliff Wells
On Thu, 2007-12-13 at 19:02 +0300, Kir Kolyshkin wrote: > OK, here's what I found concerning ubuntu-7.10 VE vs. OpenVZ. > This was fixed in an updated ubuntu templates that I just uploaded to > http://download.openvz.org/template/precreated/. These templates are now > back to using tmpfs for som

Re: [Users] VE fails to stop

2007-12-13 Thread Cliff Wells
On Thu, 2007-12-13 at 19:02 +0300, Kir Kolyshkin wrote: > OK, here's what I found concerning ubuntu-7.10 VE vs. OpenVZ. Seems to work fine. Minor nit would be the unknown group 11. I did a 'find -gid 11' and it turned up a bunch of /dev/fd* stuff with that GID, but chowning them to root didn't g

Re: [Users] VE fails to stop

2007-12-14 Thread Kir Kolyshkin
Cliff Wells wrote: On Thu, 2007-12-13 at 19:02 +0300, Kir Kolyshkin wrote: OK, here's what I found concerning ubuntu-7.10 VE vs. OpenVZ. Seems to work fine. Minor nit would be the unknown group 11. I did a 'find -gid 11' and it turned up a bunch of /dev/fd* stuff with that GID, but c

Re: [Users] VE fails to stop

2007-12-14 Thread Kir Kolyshkin
Kir Kolyshkin wrote: Cliff Wells wrote: On Thu, 2007-12-13 at 19:02 +0300, Kir Kolyshkin wrote: OK, here's what I found concerning ubuntu-7.10 VE vs. OpenVZ. Seems to work fine. Minor nit would be the unknown group 11. I did a 'find -gid 11' and it turned up a bunch of /dev/fd* stuff