On 10/8/2014 5:16 PM, Arnaud Quette wrote:
Hi Leslie,

2014-09-29 17:14 GMT+02:00 Leslie Rhorer <lrho...@mygrande.net
<mailto:lrho...@mygrande.net>>:


             I just did a fresh installation of Debian Jessie on one of
    my servers, but NUT won't configure and install.  When I try to
    install, I get the following:

    Setting up nut-client (2.7.2-1+b2) ...
    Job for nut-monitor.service failed. See 'systemctl status
    nut-monitor.service' and 'journalctl -xn' for details.
    invoke-rc.d: initscript nut-client, action "start" failed.
    dpkg: error processing package nut-client (--configure):
      subprocess installed post-installation script returned error exit
    status 1
    dpkg: dependency problems prevent configuration of nut-server:
      nut-server depends on nut-client (= 2.7.2-1+b2); however:
       Package nut-client is not configured yet.

    dpkg: error processing package nut-server (--configure):
      dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of nut:
      nut depends on nut-server; however:
       Package nut-server is not configured yet.
      nut depends on nut-client; however:
       Package nut-client is not configured yet.

    dpkg: error processing package nut (--configure):
      dependency problems - leaving unconfigured
    Errors were encountered while processing:
      nut-client
      nut-server
      nut
    E: Sub-process /usr/bin/dpkg returned an error code (1)

             Running the command `systemctl status nut-monitor.service`
    returns:

    nut-monitor.service - Network UPS Tools - power device monitor and
    shutdown controller
        Loaded: loaded (/lib/systemd/system/nut-__monitor.service; disabled)
        Active: failed (Result: exit-code) since Mon 2014-09-29 10:07:58
    CDT; 2min 12s ago
       Process: 15831 ExecStart=/sbin/upsmon (code=exited, status=1/FAILURE)

    Sep 29 10:07:58 RAID-Server upsmon[15831]: fopen
    /var/run/nut/upsmon.pid: No such file or directory
    Sep 29 10:07:58 RAID-Server upsmon[15831]: Using power down flag
    file /etc/killpower
    Sep 29 10:07:58 RAID-Server upsmon[15831]: Network UPS Tools upsmon
    2.7.2
    Sep 29 10:07:58 RAID-Server upsmon[15831]: Fatal error: insufficient
    power configured!
    Sep 29 10:07:58 RAID-Server upsmon[15831]: Sum of power
    values........: 0
    Sep 29 10:07:58 RAID-Server upsmon[15831]: Minimum value
    (MINSUPPLIES): 1
    Sep 29 10:07:58 RAID-Server upsmon[15831]: Edit your upsmon.conf and
    change the values.
    Sep 29 10:07:58 RAID-Server systemd[1]: nut-monitor.service: control
    process exited, code=exited status=1
    Sep 29 10:07:58 RAID-Server systemd[1]: Failed to start Network UPS
    Tools - power device monitor and shutdown controller.
    Sep 29 10:07:58 RAID-Server systemd[1]: Unit nut-monitor.service
    entered failed state.

             I have reported a bug, but I am unsure how to proceed at
    this point. Can anyone lend some advice?



I realized that recently, and we're working on a 1rst attempt at a solution:
https://github.com/networkupstools/nut/issues/156

I was able to get it up and running by setting MINSUPPLIES to 0 in upsmon.conf and then re-configuring NUT. I think this is now a faulty system, however. With MINSUPPLIES set to zero, will NUT ever force a shutdown? If I reset the value to 1, will the system behave properly?


_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Reply via email to