Your message dated Fri, 26 Feb 2016 13:47:23 +0100 with message-id <20160226124723.GA3828@feivel> and subject line Re: Bug#794928: watchdog not started with rc5.d script after upgrade to 8.1 has caused the Debian Bug report #794928, regarding watchdog not started with rc5.d script after upgrade to 8.1 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 [email protected] immediately.) -- 794928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794928 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: watchdog Version: 5.14-3 Severity: normal Dear Maintainer, I was unsing watchdog sucessfully on a machine on which the disk controller ocasionaly hangs. After upgrading to debian 8.1 the machine keept freezing again and was not reset. I checked my runlevel => 5 I did a fresly update-rc.d for watchdog and runlevel 5 root@quasar:~# ls -l /etc/rc5.d/S16watchdog lrwxrwxrwx 1 root root 18 Jul 1 16:58 /etc/rc5.d/S16watchdog -> ../init.d/watchdog Looks right. But still: root@quasar:~# /etc/init.d/watchdog start [ ok ] Starting watchdog (via systemctl): watchdog.service. root@quasar:~# /etc/init.d/watchdog stop [ ok ] Stopping watchdog (via systemctl): watchdog.service. root@quasar:~# /etc/rc5.d/S16watchdog start [....] Starting S16watchdog (via systemctl): S16watchdog.serviceFailed to start S16watchdog.service: Unit S16watchdog.service failed to load: No such file or directory. failed! root@quasar:~# /etc/init.d/watchdog status * watchdog.service - watchdog daemon Loaded: loaded (/lib/systemd/system/watchdog.service; static) Active: active (running) since Sam 2015-08-08 09:59:54 CEST; 5s ago Process: 3796 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false (code=exited, status=1/FAILURE) Process: 3875 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec /usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS) Process: 3872 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module (code=exited, status=0/SUCCESS) Main PID: 3877 (watchdog) CGroup: /system.slice/watchdog.service `-3877 /usr/sbin/watchdog -s Aug 08 09:59:54 quasar.woody.ch watchdog[3877]: int=30s realtime=yes sync=yes soft=no mla=0 mem=0 Aug 08 09:59:54 quasar.woody.ch watchdog[3877]: ping: no machine to check Aug 08 09:59:54 quasar.woody.ch watchdog[3877]: file: no file to check Aug 08 09:59:54 quasar.woody.ch watchdog[3877]: pidfile: no server process to check Aug 08 09:59:54 quasar.woody.ch watchdog[3877]: interface: no interface to check Aug 08 09:59:54 quasar.woody.ch watchdog[3877]: temperature: no sensors to check Aug 08 09:59:54 quasar.woody.ch watchdog[3877]: test=none(0) repair=none(0) alive=/dev/watchdog heartbeat=none to=root no_act=no force=no Aug 08 09:59:54 quasar.woody.ch watchdog[3877]: watchdog now set to 60 seconds Aug 08 09:59:54 quasar.woody.ch watchdog[3877]: hardware watchdog identity: Software Watchdog Aug 08 09:59:54 quasar.woody.ch systemd[1]: Started watchdog daemon. root@quasar:~# /etc/rc5.d/S16watchdog status * S16watchdog.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) It is the same script, just the location where it is started is different. I did try to debug the init script and find some relative paths or similar, there are none. I suppose the problem is hidden in the LSB Lib that is loaded. -Benoit- -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=de_CH, LC_CTYPE=de_CH (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages watchdog depends on: ii debconf [debconf-2.0] 1.5.56 ii init-system-helpers 1.22 ii libc6 2.19-18 ii lsb-base 4.1+Debian13+nmu1 ii udev 215-17+deb8u1 watchdog recommends no packages. watchdog suggests no packages. -- Configuration Files: /etc/watchdog.conf changed: watchdog-device = /dev/watchdog realtime = yes priority = 1 interval = 30 -- debconf information: watchdog/run_keepalive: true watchdog/restart: false watchdog/module: none watchdog/run: true
--- End Message ---
--- Begin Message ---On Sat, Aug 08, 2015 at 10:01:42AM +0200, Benoit Panizzon wrote: > I was unsing watchdog sucessfully on a machine on which the disk controller > ocasionaly hangs. > > After upgrading to debian 8.1 the machine keept freezing again and was not > reset. I just uploaded a new version to unstable. It should fix your problem. Please try it, the unstable pacakge should work on Jessie too. If it does *not* solve it, please re-open the bug report. > root@quasar:~# /etc/rc5.d/S16watchdog start > [....] Starting S16watchdog (via systemctl): S16watchdog.serviceFailed to > start S16watchdog.service: Unit S16watchdog.service failed to load: No such > file or directory. > failed! The filename is used to identify the name for the service file, i.e. using the link to execute it does not work anymore when using systemd. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org Jabber: michael at xmpp dot meskes dot org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
--- End Message ---
