Re: Bug#714029: Updating base-files will cause system-reboot when watchdog is running
reassign 714029 upgrade-reports
thanks
On Tue, 25 Jun 2013, exliju wrote:
> Package: base-files
> Version: 6.0squeeze7
> Severity: important
>
> The problem occured on my internet-router. That was initially set-up when etch
> was the stable distribution, and has lived since then just by updating to the
> newest version.
> Then I updated my system to wheezy. During the update the sysklogd / klogd was
> removed:
>
> >>> /var/log/apt/history.log >>>
> Start-Date: 2013-06-18 23:23:13
> Commandline: apt-get install base-files
> Install: iproute:i386 (20120521-3+b3, automatic), libmount1:i386 (2.20.1-5.3,
> automatic), libatm1:i386 (2.5.1-1.5, automatic), libevent-2.0-5:i386
> (2.0.19-stable-3, automatic), python-setools:i386 (3.3.7-3, automatic),
> python-
> ipy:i386 (0.75-1, automatic), libtirpc1:i386 (0.2.2-5, automatic),
> libapol4:i386 (3.3.7-3, automatic), rpcbind:i386 (0.2.0-8, automatic)
> Upgrade: selinux-policy-default:i386 (0.2.20100524-7+squeeze1, 2.20110726-12),
> base-files:i386 (6.0squeeze7, 7.1wheezy1), libblkid1:i386 (2.17.2-9,
> 2.20.1-5.3), util-linux:i386 (2.17.2-9, 2.20.1-5.3), netbase:i386 (4.45, 5.0),
> policycoreutils:i386 (2.0.82-3, 2.1.10-9), ifupdown:i386 (0.6.10, 0.7.8),
> python-sepolgen:i386 (1.0.23-1, 1.1.5-3), libslang2:i386 (2.2.2-4, 2.2.4-15),
> initscripts:i386 (2.88dsf-13.1+squeeze1, 2.88dsf-41), nfs-common:i386
> (1.2.2-4squeeze2, 1.2.6-4)
> Remove: sysklogd:i386 (1.5-6), portmap:i386 (6.0.0-2), klogd:i386 (1.5-6)
> <<<
>
> Problem was, that I had running the watchdog with the option to monitor the
> pid-file for a running syslog (/etc/watchdog.conf:
> pidfile=/var/run/syslogd.pid)
> So, when the update comes to the point to stop the running syslog, the
> watchdog
> does what it was designed for: Rebooting the system.
>
> Problem 1 was, that this leaves the update unfinished.
> Problem 2 was, that after rebooting this immediatly happened again (as
> /var/run/syslogd.pid doesn't point to a running process anymore). So reboot
> again.
>
> I don't know if this is a base-files, sysklogd, klogd, watchdog or some
> general
> "update to wheezy" problem. But as it happend when updating base-files I filed
> it here.
>
> My proposal:
> Before stopping the (sys)klogd do a check, if watchdog is running and
> monitoring the pidfile.
> If so, give the user a hint, and allow to stop the update.
> I'm not unix-hacker enough to know, but probably it's possible to detect,
> which
> processes monitor the pid-file, and show those processes to the user.
The normal syslog package in wheezy is rsyslog, so it should not be a
surprise that the old syslog packages are removed during the upgrade.
I didn't know about the watchdog package, but reading the description,
it seems to me a very dangerous piece of software to have it running during
an upgrade, so this could well be a feature more than a bug.
You admit that watchdog did what it was told to do, which is to reboot the
system. Are you sure you wanted to reboot the system in the middle of an
upgrade?
Anyway, base-files is unlikely to blame for this, as it does not stop
or start system processes. I'm reassigning this to "upgrade-reports",
hoping that the maintainer of such virtual package may analyze this
and reassign the report more accurately.
Thanks.
Reply to: