From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1008 Path: news.gmane.org!not-for-mail From: Gerrit Pape Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: runit upgrades and halt rather than reboot Date: Fri, 3 Feb 2006 16:55:52 +0000 Message-ID: <20060203165552.17710.qmail@238ebfa254faf9.315fe32.mid.smarden.org> References: <20060202042050.GI17576@annvix.org> <20060203154031.9374.qmail@6824f200d7859c.315fe32.mid.smarden.org> <20060203164529.GK17576@annvix.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138985839 2385 80.91.229.2 (3 Feb 2006 16:57:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 3 Feb 2006 16:57:19 +0000 (UTC) Original-X-From: supervision-return-1244-gcsg-supervision=m.gmane.org@list.skarnet.org Fri Feb 03 17:57:11 2006 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1F54Dc-0001SE-8v for gcsg-supervision@gmane.org; Fri, 03 Feb 2006 17:55:32 +0100 Original-Received: (qmail 27568 invoked by uid 76); 3 Feb 2006 16:55:53 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 27563 invoked from network); 3 Feb 2006 16:55:53 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20060203164529.GK17576@annvix.org> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1008 Archived-At: On Fri, Feb 03, 2006 at 09:45:29AM -0700, Vincent Danen wrote: > * Gerrit Pape [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.