Re: runit upgrades and halt rather than reboot

[Vincent Danen <vdanen@linsec.ca>]

[-- Attachment #1: Type: text/plain, Size: 3709 bytes --]

* Gerrit Pape <pape@smarden.org> [2006-02-03 16:55:52 +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.

Ok, maybe I'm missing something, but the inode is different on the copy.

[root@cerberus sbin]# cp init init.org
[root@cerberus sbin]# ls -i init init.org
6374308 init*  6301334 init.org*

But then if I do:

[root@cerberus sbin]# cp /bin/ls init.org
[root@cerberus sbin]# ls -i init.org
6301334 init.org*

So even though the contents of init.org have drastically changed, the
inode is still the same.  The same would obviously hold true for init,
when it's replaced during an rpm upgrade.

I don't think it solves the problem (I did try a few days ago and it
still halted the system), but maybe this explains the why; the copy
apparently isn't needed it we're trying to preserve the inode, or is
there a way to copy a file by specifying the inode?  I'll admit I'm a
bit out of my depth on this one (no options seemed to present themself
from cp --help).

If there is one thing that is problematic for me (and Annvix users) is
that runit, when it is upgraded, always halts the system.  There has to
be a way to fix this.  It's my one last great bug.  =)

Any ideas at all, from anyone, would be greatly appreciated.

> > 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

Yup, that would do it, but I'm not convinced the old file makes a
difference.  I'm going to try again (via the rpm package rather than
manually copying) to see if it makes a difference.

-- 
Annvix - Secure Linux Server: http://annvix.org/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FEE30AD4 : 7F6C A60C 06C2 4811 FA1C  A2BC 2EBC 5E32 FEE3 0AD4}
Wasting time like it was free...

[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]