Package: nut-client Version: 2.7.4-8 Severity: minor Dear Maintainer,
When upgrading the system from Stretch to Buster, the final stage of updating nut-client failed. The output is shown below. As a workaround, I set MINSUPPLIES = 0 in /etc/nut/upsmon.conf which solved the problem. After upgrade, upsmon (nut-monitor.service) was enabled and running even though I had explicitly disabled it when I originally installed nut. Setting up nut-client (2.7.4-8) ... Job for nut-monitor.service failed because the control process exited with error code. See "systemctl status nut-monitor.service" and "journalctl -xe" for details. invoke-rc.d: initscript nut-client, action "restart" failed. ● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-07-09 23:05:52 EEST; 9ms ago Process: 6207 ExecStart=/sbin/upsmon (code=exited, status=1/FAILURE) july 09 23:05:52 hostname upsmon[6207]: fopen /var/run/nut/upsmon.pid: No such file or directory july 09 23:05:52 hostname upsmon[6207]: Using power down flag file /etc/killpower july 09 23:05:52 hostname upsmon[6207]: Network UPS Tools upsmon 2.7.4 july 09 23:05:52 hostname upsmon[6207]: Fatal error: insufficient power configured! july 09 23:05:52 hostname upsmon[6207]: Sum of power values........: 0 july 09 23:05:52 hostname upsmon[6207]: Minimum value (MINSUPPLIES): 1 july 09 23:05:52 hostname upsmon[6207]: Edit your upsmon.conf and change the values. july 09 23:05:52 hostname systemd[1]: nut-monitor.service: Control process exited, code=exited, status=1/FAILURE july 09 23:05:52 hostname systemd[1]: nut-monitor.service: Failed with result 'exit-code'. july 09 23:05:52 hostname systemd[1]: Failed to start Network UPS Tools - power device monitor and shutdown controller. dpkg: error processing package nut-client (--configure): installed nut-client package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of nut: nut depends on nut-client; however: Package nut-client is not configured yet. dpkg: error processing package nut (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of nut-server: nut-server depends on nut-client (= 2.7.4-8); however: Package nut-client is not configured yet. dpkg: error processing package nut-server (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: nut-client nut nut-server E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nut-client depends on: ii adduser 3.118 ii libc6 2.28-10 ii libupsclient4 2.7.4-8 ii lsb-base 10.2019051400 Versions of packages nut-client recommends: ii bash-completion 1:2.8-6 Versions of packages nut-client suggests: pn nut-monitor <none> -- Configuration Files: /etc/nut/nut.conf [Errno 13] Lupa evätty: '/etc/nut/nut.conf' /etc/nut/upsmon.conf [Errno 13] Lupa evätty: '/etc/nut/upsmon.conf' /etc/nut/upssched.conf [Errno 13] Lupa evätty: '/etc/nut/upssched.conf' -- no debconf information
