On Mon, Jul 12, 2010 at 05:10:08PM +0200, Josef Johansson wrote:
> My own services doesn't start for some reason, and I try to debug it
> now by using
> # /etc/vservers/.defaults/apps/vshelper
> * debug
> When existing, the vshelper execution will be traced.
> * disabled
> When existing, the vshelper functionality will be disabled for
> all vservers.
> * logfile
> The file where output will be logged to when vshelper is invoked
> from the kernel. This should point somewhere e.g. into /var/log.
> * warning-disabled
> When existing, sanity checks for the vshelper functionality will
> be skipped.
> * /etc/vservers/.defaults/apps/vshelper/vshelper-methods
> o handler
> See vshelper/action.
> from http://www.nongnu.org/util-vserver/doc/conf/configuration.html
> maybe we could compare logs? see me attached log.
> I didn't get anything on vserver $server start though, this is just
> vserver $server stop.
the attached log is from 'vserver $server restart' and
it spawns an async restart handler which is not logged
and a 'kill after timeout' which kicks in after the
timeout (i.e. your guest refuses to shut down properly)
but I may have missed the obvious, Daniel propably
knows a lot more about those logs ...
btw, what util-vserver and kernel/patch version as well
as guest init style and distribution?
best,
Herbert
> ________________________________________
> Från: Dan Urist [durist@ucar.edu]
> Skickat: den 12 juli 2010 17:03
> Till: vserver@list.linux-vserver.org
> Ämne: Re: [vserver] vserver stop fails with upstart guest
>
> On Mon, 12 Jul 2010 16:43:25 +0200
> Josef Johansson <josef@ilait.se> wrote:
>
> > Just to check, have you commented out these?
> >
> > rc.conf:console output
> > rc.conf:env INIT_VERBOSE
> > rc-sysinit.conf:console output
> > rc-sysinit.conf:env INIT_VERBOSE
> >
> > Regards
>
> I didn't have the env lines commented out, but I've tried that now and
> it's still timing out on vserver stop. Thanks for the suggestion,
> though.
>
>
> >
> > ________________________________________
> > Från: Dan Urist [durist@ucar.edu]
> > Skickat: den 8 juli 2010 16:29
> > Till: vserver@list.linux-vserver.org
> > Ämne: 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
>
>
>
> --
> Dan Urist
> durist@ucar.edu
> 303-497-2459
Received on Mon Jul 12 18:11:40 2010