Package: nut
Version: 2.6.4-1
Severity: minor
Dear Maintainer,
* What led up to the situation?
Upgrate of nut: 2012-06-16 14:50:02 upgrade nut:all 2.6.3-1 2.6.4-1
* What exactly did you do (or not do) that was effective (or
ineffective)?
Reboot.
* What was the outcome of this action?
nut init scripts failed.
/etc/init.d/nut completed successfully and started everything (drv, upsd,
upsmon), but
subsequently started /etc/init.d/nut-{server,client} failed because of
upsd and upsmon.
Checking the status after logging in shows that all parts are running.
* What outcome did you expect instead?
Successful start of all init scripts as before the upgrade.
* Fix?
I removed the /etc/init.d/nut init script (update-rc.d nut remove) as it
seemed from an
earlier time and possibly left over:
$ ls -l /etc/init.d/nut*
-rwxr-xr-x 1 root root 5345 Jan 24 06:17 /etc/init.d/nut
-rwxr-xr-x 1 root root 5273 Jun 6 14:06 /etc/init.d/nut-client
-rwxr-xr-x 1 root root 5271 Jun 6 14:06 /etc/init.d/nut-server
This fixed the problem, subsequent reboots completed without failure.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
