On Dec 16, Michael Meskes wrote:
> What happens if you stop watchdog, does the process go away? Or if you happen 
> to reboot, does that change things? I'm wondering if the old process stays in 
> the way and thus may need to be killed manually. I have it that before, that 
> processes do not disappear despite being stopped via systemctl.

No, the process is stopped properly. systemctl start and stop
work as expected, only systemctl restart fails.


Stop / start:

  # systemctl status watchdog
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
     Active: active (running) since Thu 2014-12-11 14:44:09 CET; 4 days ago
   Main PID: 30954 (watchdog)
     CGroup: /system.slice/watchdog.service
             └─30954 /usr/sbin/watchdog

  Dec 11 14:44:09 grappa watchdog[30954]: starting daemon (5.14):
  Dec 11 14:44:09 grappa watchdog[30954]: int=1s realtime=yes sync=no soft=no 
mla=0 mem=0
  Dec 11 14:44:09 grappa watchdog[30954]: ping: no machine to check
  Dec 11 14:44:09 grappa watchdog[30954]: file: no file to check
  Dec 11 14:44:09 grappa watchdog[30954]: pidfile: no server process to check
  Dec 11 14:44:09 grappa watchdog[30954]: interface: no interface to check
  Dec 11 14:44:09 grappa watchdog[30954]: temperature: no sensors to check
  Dec 11 14:44:09 grappa watchdog[30954]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  Dec 11 14:44:09 grappa watchdog[30954]: cannot set timeout 60 (errno = 22 = 
'Invalid argument')
  Dec 11 14:44:09 grappa watchdog[30954]: hardware watchdog identity: INTCAMT
  # ps ax|grep watchdog
     10 ?        S      0:01 [watchdog/0]
     11 ?        S      0:02 [watchdog/1]
  28719 pts/4    S+     0:00 grep watchdog
  30954 ?        SLs    0:17 /usr/sbin/watchdog

  # systemctl stop watchdog
  # systemctl status watchdog
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
     Active: inactive (dead) since Tue 2014-12-16 13:32:38 CET; 7s ago
    Process: 28726 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false 
(code=exited, status=1/FAILURE)
   Main PID: 30954 (code=exited, status=0/SUCCESS)

  Dec 11 14:44:09 grappa watchdog[30954]: file: no file to check
  Dec 11 14:44:09 grappa watchdog[30954]: pidfile: no server process to check
  Dec 11 14:44:09 grappa watchdog[30954]: interface: no interface to check
  Dec 11 14:44:09 grappa watchdog[30954]: temperature: no sensors to check
  Dec 11 14:44:09 grappa watchdog[30954]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  Dec 11 14:44:09 grappa watchdog[30954]: cannot set timeout 60 (errno = 22 = 
'Invalid argument')
  Dec 11 14:44:09 grappa watchdog[30954]: hardware watchdog identity: INTCAMT
  Dec 16 13:32:33 grappa watchdog[30954]: stopping daemon (5.14)
  Dec 16 13:32:38 grappa systemd[1]: watchdog.service: control process exited, 
code=exited status=1
  Dec 16 13:32:38 grappa systemd[1]: Unit watchdog.service entered failed state.
  # ps ax|grep watchdog
     10 ?        S      0:01 [watchdog/0]
     11 ?        S      0:02 [watchdog/1]
  28746 pts/4    S+     0:00 grep watchdog

  # systemctl start watchdog
  # systemctl status watchdog
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
     Active: active (running) since Tue 2014-12-16 13:32:59 CET; 20s ago
    Process: 28726 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false 
(code=exited, status=1/FAILURE)
    Process: 28756 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 28753 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 28758 (watchdog)
     CGroup: /system.slice/watchdog.service
             └─28758 /usr/sbin/watchdog

  Dec 16 13:32:59 grappa watchdog[28758]: starting daemon (5.14):
  Dec 16 13:32:59 grappa watchdog[28758]: int=1s realtime=yes sync=no soft=no 
mla=0 mem=0
  Dec 16 13:32:59 grappa watchdog[28758]: ping: no machine to check
  Dec 16 13:32:59 grappa watchdog[28758]: file: no file to check
  Dec 16 13:32:59 grappa watchdog[28758]: pidfile: no server process to check
  Dec 16 13:32:59 grappa watchdog[28758]: interface: no interface to check
  Dec 16 13:32:59 grappa watchdog[28758]: temperature: no sensors to check
  Dec 16 13:32:59 grappa watchdog[28758]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  Dec 16 13:32:59 grappa watchdog[28758]: cannot set timeout 60 (errno = 22 = 
'Invalid argument')
  Dec 16 13:32:59 grappa watchdog[28758]: hardware watchdog identity: INTCAMT
  # ps ax|grep watchdog
     10 ?        S      0:01 [watchdog/0]
     11 ?        S      0:02 [watchdog/1]
  28758 ?        SLs    0:00 /usr/sbin/watchdog
  28762 pts/4    S+     0:00 grep watchdog


Restart:

  # systemctl restart watchdog
  Job for watchdog.service canceled.
  # systemctl status watchdog
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
     Active: inactive (dead) since Tue 2014-12-16 13:34:04 CET; 6s ago
    Process: 28766 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false 
(code=exited, status=1/FAILURE)
    Process: 28756 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 28753 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 28758 (code=exited, status=0/SUCCESS)

  Dec 16 13:32:59 grappa watchdog[28758]: file: no file to check
  Dec 16 13:32:59 grappa watchdog[28758]: pidfile: no server process to check
  Dec 16 13:32:59 grappa watchdog[28758]: interface: no interface to check
  Dec 16 13:32:59 grappa watchdog[28758]: temperature: no sensors to check
  Dec 16 13:32:59 grappa watchdog[28758]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  Dec 16 13:32:59 grappa watchdog[28758]: cannot set timeout 60 (errno = 22 = 
'Invalid argument')
  Dec 16 13:32:59 grappa watchdog[28758]: hardware watchdog identity: INTCAMT
  Dec 16 13:33:59 grappa watchdog[28758]: stopping daemon (5.14)
  Dec 16 13:34:04 grappa systemd[1]: watchdog.service: control process exited, 
code=exited status=1
  Dec 16 13:34:04 grappa systemd[1]: Unit watchdog.service entered failed state.
  # ps ax|grep watchdog
     10 ?        S      0:01 [watchdog/0]
     11 ?        S      0:02 [watchdog/1]
  28783 pts/4    S+     0:00 grep watchdog


> > PS: The old config file /etc/default/watchdog seems not to be
> > properly removed from the package, dpkg -s still lists it (as
> > obsolete). See also the "Configuration Files" section below.

The config file is still referenced in the package database:

  # dpkg -S /etc/default/watchdog
  watchdog: /etc/default/watchdog

  # dpkg -s watchdog
  Package: watchdog
  Status: install ok installed
  Priority: extra
  Section: admin
  Installed-Size: 196
  Maintainer: Michael Meskes <mes...@debian.org>
  Architecture: i386
  Version: 5.14-3
  Depends: libc6 (>= 2.7), debconf (>= 0.5) | debconf-2.0, init-system-helpers 
(>= 1.18~), makedev (>= 2.3.1-24) | udev, lsb-base (>= 3.2-14)
  Conffiles:
   /etc/init.d/watchdog 350ab37d9e081970c491adb488c29d17
   /etc/init.d/wd_keepalive d2f8e84bd91ffd2c5b5ac07774fb751b
   /etc/watchdog.conf bd071fbb51fb2f9ee807af043111ba27
   /etc/default/watchdog f6517ce4745ab05fd8cd4da1a39e5906 obsolete
  Description: system health checker and software/hardware watchdog handler

There's a mechanism to properly remove a config file from the
package database on a package upgrade, but I don't know the
details.

I'm going to purge and reinstall the package, that should at
least solve the problem of the obsolete config file locally.

Regards

Uwe


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to