Package: watchdog
Version: 5.14-3
Severity: important

Dear Maintainer,

the watchdog package fails to upgrade (from version 5.14-2):

  Setting up watchdog (5.14-3) ...
  /run/udev or .udevdb or .udev presence implies active udev.  Aborting MAKEDEV 
invocation.
  Job for watchdog.service canceled.
  invoke-rc.d: initscript watchdog, action "restart" failed.
  dpkg: error processing package watchdog (--configure):
   subprocess installed post-installation script returned error exit status 1

Trying to recover at the end of the aptitude run fails too:

  Errors were encountered while processing:
   watchdog
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Failed to perform requested operation on package.  Trying to recover:
  Setting up watchdog (5.14-3) ...
  /run/udev or .udevdb or .udev presence implies active udev.  Aborting MAKEDEV 
invocation.

Also when I try to restart watchdog manually I end up with no
watchdog process running:

  # systemctl status watchdog.service
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
     Active: active (running) since Thu 2014-12-11 14:27:42 CET; 22s ago
    Process: 29018 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false 
(code=exited, status=1/FAILURE)
    Process: 29042 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 29040 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 29044 (watchdog)
     CGroup: /system.slice/watchdog.service
             └─29044 /usr/sbin/watchdog

  # systemctl restart watchdog.service
  Job for watchdog.service canceled.
  # systemctl status -l watchdog.service
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
     Active: inactive (dead) since Thu 2014-12-11 14:30:15 CET; 33s ago
    Process: 29639 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false 
(code=exited, status=1/FAILURE)
    Process: 29042 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 29040 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 29044 (code=exited, status=0/SUCCESS)

  Dec 11 14:30:10 grappa watchdog[29044]: stopping daemon (5.14)
  Dec 11 14:30:15 grappa systemd[1]: watchdog.service: control process exited, 
code=exited status=1
  Dec 11 14:30:15 grappa systemd[1]: Unit watchdog.service entered failed state.

Using only the start command works, but ends up with status
1/FAILURE for the service:

  # systemctl start watchdog.service
  # systemctl status -l watchdog.service
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
     Active: active (running) since Thu 2014-12-11 14:31:35 CET; 15s ago
    Process: 29639 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false 
(code=exited, status=1/FAILURE)
    Process: 29675 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 29673 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 29678 (watchdog)
     CGroup: /system.slice/watchdog.service
             └─29678 /usr/sbin/watchdog

  Dec 11 14:31:35 grappa watchdog[29678]: starting daemon (5.14):
  Dec 11 14:31:35 grappa watchdog[29678]: int=1s realtime=yes sync=no soft=no 
mla=0 mem=0
  Dec 11 14:31:35 grappa watchdog[29678]: ping: no machine to check
  Dec 11 14:31:35 grappa watchdog[29678]: file: no file to check
  Dec 11 14:31:35 grappa watchdog[29678]: pidfile: no server process to check
  Dec 11 14:31:35 grappa watchdog[29678]: interface: no interface to check
  Dec 11 14:31:35 grappa watchdog[29678]: temperature: no sensors to check
  Dec 11 14:31:35 grappa watchdog[29678]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  Dec 11 14:31:35 grappa watchdog[29678]: cannot set timeout 60 (errno = 22 = 
'Invalid argument')
  Dec 11 14:31:35 grappa watchdog[29678]: hardware watchdog identity: INTCAMT

I'm not sure what the correct severity for this bug should be
(I would consider it RC, so "serious"?). Please adjust the
severity as needed.

Regards

Uwe


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.


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
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.54
ii  init-system-helpers    1.22
ii  libc6                  2.19-13
ii  lsb-base               4.1+Debian13+nmu1
ii  makedev                2.3.1-93
ii  udev                   215-7

watchdog recommends no packages.

watchdog suggests no packages.

-- Configuration Files:
/etc/default/watchdog f6517ce4745ab05fd8cd4da1a39e5906 [Errno 2] No such file 
or directory: u'/etc/default/watchdog f6517ce4745ab05fd8cd4da1a39e5906'
/etc/watchdog.conf changed:
watchdog-device = /dev/watchdog
realtime                = yes
priority                = 1


-- debconf information:
* watchdog/module: none
* watchdog/run_keepalive: true
* watchdog/restart: true
* watchdog/run: true


-- 
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