Re: [vserver] vserver stop fails with upstart guest

Thanks for the suggestion, but I have the vserver.conf file.

The easiest (ugly) solution is probably to hack up the pacemaker
resource agent so it tries both methods of stopping the vserver.

On Thu, 8 Jul 2010 08:42:47 +0200
Josef Johansson <josef@ilait.se> wrote:

> I always find that i forgot to add the vserver.conf file to etc init.
>
> Dan Urist <durist@ucar.edu> skrev:
>
>
> I'm running a debian lenny kernel with ubuntu guests. I'm currently
> trying to upgrade a guest from jaunty to lucid, which uses the new
> upstart init style. I've followed the guide on the wiki (set init
> style to plain, etc.), and the guest now starts properly and runs
> fine.
>
> My problem is "vserver stop" doesn't work; it times out and eventually
> kills the vserver. I can shut down the vserver cleanly with "telinit
> 0" or "shutdown -h now" from within the vserver, or by using one of
> those commands with "vserver exec". The reason this is a problem for
> me is I'm running these vservers under a pacemaker cluster, and the
> resource agent uses the vserver command to manage the vservers. I'm
> going to have a mixture of jaunty and lucid guests for awhile, and
> "telinit 0" or "shutdown -h now" doesn't work for the jaunty guests
> (I get "shutdown: Unable to send message: Connection refused"), so
> changing the resource agent to use one of those won't work.
>
> Is there some way to make the "vserver stop" command work with lucid
> (upstart) guests? Is this an issue with the "plain" init style?
> --
> Dan Urist
> durist@ucar.edu
> 303-497-2459

-- 
Dan Urist
durist@ucar.edu
303-497-2459