From: Gerrit Pape <pape@smarden.org>
Subject: Re: runit upgrades and halt rather than reboot
Date: Fri, 3 Feb 2006 16:55:52 +0000 [thread overview]
Message-ID: <20060203165552.17710.qmail@238ebfa254faf9.315fe32.mid.smarden.org> (raw)
In-Reply-To: <20060203164529.GK17576@annvix.org>
On Fri, Feb 03, 2006 at 09:45:29AM -0700, Vincent Danen wrote:
> * Gerrit Pape <pape@smarden.org> [2006-02-03 15:40:31 +0000]:
> > > I'm encountering a really odd problem. When I upgrade runit, when I do
> > > a "reboot" or "init 6", runit goes into poweroff mode rather than
> > > reboot. I'm gearing up to put out my next version of Annvix so am doing
> > > some testing and we upgraded from runit 1.3.1 to 1.3.3 and on each test
> > > instance (2 x86 and 1 x86_64), once all the packages were upgraded
> > > (including runit), when I did reboot (the first two) and "init 6" (the
> > > last one), they powered off.
> > >
> > > I'm not sure if this is because the /sbin/init binary changed or what,
> > > but it's *really* annoying, particularly since I know some folks who use
> > > Annvix at remote locations (myself as well) and a trip to the colo to
> > > turn the machine on after the upgrade would, well, stink. =)
> > >
> > > Any ideas as to what might be the problem and how I can rectify it?
> > > After that reboot, runit is fine... reboot works as advertised, as does
> > > halt, etc. But it's just that one reboot after it's been upgraded that
> > > is problematic.
> >
> > I'm not sure from your description. With a preliminary runit Debian
> > package, on shutdown after package upgrade, the root filesystem wasn't
> > unmounted cleanly, because /sbin/runit was replaced. The workaround is
> > to first copy /sbin/runit to /sbin/runit.old, then replace /sbin/runit.
> > After reboot, /sbin/runit.old can be removed again. Maybe it's worth a
> > try.
>
> Hmmm... that might not be a bad idea to try. So instead of running
> reboot/halt/shutdown, run "init.old 6" (I renamed runit to init).
No, you can still use `init 6` with the new binary. It's just that the
old, still running, /sbin/init still has an inode on the filesystem;
that's what the copy is for. I'm not sure it solves your problem
though.
> I'll give that a try, Gerrit. It makes things a bit messy, but nothing
> a startup script can't check for and cleanup.
I have this in /etc/runit/1
rm -f /sbin/runit.old
Regards, Gerrit.
next prev parent reply other threads:[~2006-02-03 16:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 4:20 Vincent Danen
2006-02-03 15:40 ` Gerrit Pape
2006-02-03 16:45 ` Vincent Danen
2006-02-03 16:55 ` Gerrit Pape [this message]
2006-02-03 17:04 ` Vincent Danen
2006-02-11 19:03 ` Vincent Danen
2006-02-11 19:11 ` Paul Jarc
2006-02-11 19:44 ` Vincent Danen
2006-02-13 14:44 ` Gerrit Pape
2006-02-14 4:08 ` Vincent Danen
2006-02-14 5:22 ` Joshua N Pritikin
2006-02-14 5:42 ` copy runit-init to /sbin/init or not Alex Efros
2006-02-14 6:04 ` Vincent Danen
2006-02-14 14:08 ` Alex Efros
2006-02-14 18:49 ` Vincent Danen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060203165552.17710.qmail@238ebfa254faf9.315fe32.mid.smarden.org \
--to=pape@smarden.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).