[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#714029: marked as done (Updating base-files will cause system-reboot when watchdog is running)

Your message dated Mon, 24 Nov 2014 12:57:24 +0100
with message-id <201411241257.25635.holger@layer-acht.org>
and subject line watchdog did what it was configured to do
has caused the Debian Bug report #714029,
regarding Updating base-files will cause system-reboot when watchdog is running
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
714029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714029
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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.

Kind regards.
Ekkehard



-- System Information:
Debian Release: 6.0.7
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages base-files depends on:
ii gawk [awk] 1:3.1.7.dfsg-5 GNU awk, a pattern scanning and pr ii mawk [awk] 1.3.3-15 a pattern scanning and text proces 

base-files recommends no packages.

base-files suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi Ekkehard,

thanks for your upgrade-report.

As explained by Santiago, the removal of sysklogd was to be expected (the 
package is not part of the wheezy release) and you configured the watchdog to 
restart the computer if sysklogd was not running, and then the watchdog did 
what it was told to do, thus closing.

(Granted, this could have been a wishlist bug against the watchdog package 1.5 
years ago, but I don't think keeping this bug open and reassigning it to the 
watchdog package is still useful today, to add code special casing a package 
removal almost two releases ago. Especially as it needs user configuration to 
do harm...)

I hope you agree! :-)


cheers,
	Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: