Nut upsuser - Oct 2017 - debian 8 "jessie" nut 2.7.2 slaves not shutting down

OS name and version,
                MASTER SYSTEM has three APC smart UPS 3000 UPS connected via USB
                                debian 8 "jessie" Linux pdxvhtst01
3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux
                SLAVE SYSTEMS monitoring MASTER via IP
                                debian 8 "jessie" Linux geaaetst01
3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux
                                debian 8 "jessie" Linux pdxvhtst02
3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux

exact NUT version,
                Network UPS Tools upsmon 2.7.2

NUT installation method: from source tarball, package or Subversion,
                installed from package

exact device name and related information (manufacturing date, web pointers,
...),
                device.mfr: American Power Conversion
                device.model: Smart-UPS 3000
                device.type: ups
                driver.name: usbhid-ups
                driver.version: 2.7.2
                driver.version.data: APC HID 0.95
                driver.version.internal: 0.38
                ups.firmware: UPS 06.5 / ID=18
                ups.mfr: American Power Conversion
                ups.mfr.date: 2013/02/25
                ups.model: Smart-UPS 3000
                ups.productid: 0003
                ups.vendorid: 051d

complete problem description, with any relevant traces, like system log
excerpts, and driver debug output. You can obtain the latter using the following
command, as root and after having stopped NUT:
                there are three APC smart ups connected via usb cables to the
master system, the master system shuts down as expected but the slave systems
never shutdown eventhough I believe that all the configs are properly set the
slaves should either shutdown when there is only one ups and it is running low
on battery power offline or worst case shutdown after they cannot communicate
with the master for longer than the HOSTSYNC 15 or UPS for longer than the
DEADTIME 15


[otakHG_sigLogo]

Drew Plaster | Systems Administrator
808 SW 3rd Avenue, Suite 300 | Portland, OR 97204
o: 503.415.2385 | c: 503.484.0168 | f: 503.415.2498
www.otak.com<http://www.otak.com>

P at Otak, we consider the environment before printing emails.

Disclaimer:
The information transmitted in this e-mail message and attachments, if any, may
contain confidential material, and is intended only for the use of the
individual or entity named above. Distribution to, or review by, unauthorized
persons is prohibited. In the event of the unauthorized use of any material in
this transmission, neither Otak nor the sender shall have any liability and the
recipient shall defend, indemnify and hold harmless the sender, Otak and its
principals, agents, employees and subconsultants from all related claims and
damages. The recipient understands and agrees that any use or distribution of
the material in this transmission is conditioned upon the acceptance of the
terms stated in this disclaimer. If you have received this transmission in
error, immediately notify the sender and permanently delete this transmission
including attachments, if any.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20171018/612fdca6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1762 bytes
Desc: image001.jpg
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20171018/612fdca6/attachment.jpg>

On Wed, 18 Oct 2017, Drew Plaster wrote:
> ??????????????? there are three APC smart ups connected via usb cables 
> to the master system, the master system shuts down as expected but the 
> slave systems never shutdown eventhough I believe that all the configs 
> are properly set the slaves should either shutdown when there is only 
> one ups and it is running low on battery power offline or worst case 
> shutdown after they cannot communicate with the master for longer than 
> the HOSTSYNC 15 or UPS for longer than the DEADTIME 15
Hi, Could you show us your NUT configuration files?  Please omit the 
comments, and double spacing will not be needed.

Roger
> Disclaimer: The information transmitted in this e-mail message and 
> attachments, if any, may contain confidential material, and is intended 
> only for the use of the individual or entity named above....
It's probably best not to send such a disclaimer to a public mailing list 
with hundreds of subscribers.

MASTER SYSTEM

	nut.conf
MODE=netserver

	ups.conf
 [TOPAPC]
     driver = usbhid-ups
       port = auto
      pollonly
      serial = "IS1309002707"
      desc = "TOPAPC"
 [MIDAPC]
       driver = usbhid-ups
         port = auto
        pollonly
        serial = "IS1309001233"
        desc = "MIDAPC"
 [BOTAPC]
       driver = usbhid-ups
         port = auto
        pollonly
        serial = "IS1309001213"
        desc = "BOTAPC"

	upsd.conf
 LISTEN 127.0.0.1 3493
 LISTEN 172.16.1.158 3493

	upsd.users
        [admin]
                password = XXXXXXXXX
                actions = SET
                instcmds = ALL
        [user]
                password  = XXXXXXXXX
                instcmds  = ALL
        [upsmon]
                password  = XXXXXXXXX
                upsmon master
        [upsmonslave]
                password = XXXXXXXXX
                upsmonslave slave
        [geaaetst01]
                password = XXXXXXXXX
                geaaetst01 slave
        [pdxvhtst02]
                password = XXXXXXXXX
                pdxvhtst02 slave

	upsmon.conf
 MONITOR TOPAPC at localhost 1 upsmon pass master
 MONITOR MIDAPC at localhost 1 upsmon pass master
 MONITOR BOTAPC at localhost 1 upsmon pass master
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h now"
 NOTIFYCMD /bin/notifynetadmins
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
 NOTIFYMSG ONLINE       "UPS %s on line power"
 NOTIFYMSG ONBATT       "UPS %s on battery"
 NOTIFYMSG LOWBATT      "UPS %s battery is low"
 NOTIFYMSG FSD          "UPS %s: forced shutdown in progress"
 NOTIFYMSG COMMOK       "Communications with UPS %s established"
 NOTIFYMSG COMMBAD      "Communications with UPS %s lost"
 NOTIFYMSG SHUTDOWN     "Auto logout and shutdown proceeding"
 NOTIFYMSG REPLBATT     "UPS %s battery needs to be replaced"
 NOTIFYMSG NOCOMM       "UPS %s is unavailable"
 NOTIFYMSG NOPARENT     "upsmon parent process died - shutdown
impossible"
 NOTIFYFLAG ONLINE      EXEC+SYSLOG+WALL
 NOTIFYFLAG ONBATT      EXEC+SYSLOG+WALL
 NOTIFYFLAG LOWBATT     EXEC+SYSLOG+WALL
 NOTIFYFLAG FSD EXEC+SYSLOG+WALL
 NOTIFYFLAG COMMOK      EXEC+SYSLOG+WALL
 NOTIFYFLAG COMMBAD     EXEC+SYSLOG+WALL
 NOTIFYFLAG SHUTDOWN    EXEC+SYSLOG+WALL
 NOTIFYFLAG REPLBATT    EXEC+SYSLOG+WALL
 NOTIFYFLAG NOCOMM      EXEC+SYSLOG+WALL
 NOTIFYFLAG NOPARENT    EXEC+SYSLOG+WALL
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5

	upssched.conf
CMDSCRIPT /bin/upssched-cmd

	SLAVE SYSTEM (1)

	nut.conf
MODE=netclient

	upsmon.conf
 MONITOR TOPAPC at 172.16.1.158 1 geaaetst01 pass slave
 MONITOR MIDAPC at 172.16.1.158 1 geaaetst01 pass slave
 MONITOR BOTAPC at 171.16.1.158 1 geaaetst01 pass slave
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h now"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 1

	upssched.conf
CMDSCRIPT /bin/upssched-cmd

	SLAVE SYSTEM (2)

	nut.conf
MODE=netclient

	upsmon.conf
 MONITOR TOPAPC at 172.16.1.158 1 pdxvhtst02 pass slave
 MONITOR MIDAPC at 172.16.1.158 1 pdxvhtst02 pass slave
 MONITOR BOTAPC at 171.16.1.158 1 pdxvhtst02 pass slave
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h now"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 1

	upssched.conf
CMDSCRIPT /bin/upssched-cmd

?
Drew Plaster | Systems Administrator
808 SW 3rd Avenue, Suite 300 |?Portland, OR 97204
o: 503.415.2385 |?c: 503.484.0168 | f:?503.415.2498
www.otak.com
?
??at Otak, we consider the environment before printing emails.
?
Disclaimer:
The information transmitted in this e-mail message and attachments, if any, may
contain confidential material, and is intended only for the use of the
individual or entity named above. Distribution to, or review by, unauthorized
persons is prohibited. In the event of the unauthorized use of any material in
this transmission, neither Otak nor the sender shall have any liability and the
recipient shall defend, indemnify and hold harmless the sender, Otak and its
principals, agents, employees and subconsultants from all related claims and
damages. The recipient understands and agrees that any use or distribution of
the material in this transmission is conditioned upon the acceptance of the
terms stated in this disclaimer. If you have received this transmission in
error, immediately notify the sender and permanently delete this?transmission
including attachments, if any.

-----Original Message-----
From: Nut-upsuser [mailto:nut-upsuser-bounces+drew.plaster=otak.com at
lists.alioth.debian.org] On Behalf Of Roger Price
Sent: Wednesday, October 18, 2017 12:54 PM
To: nut-upsuser Mailing List
Subject: Re: [Nut-upsuser] debian 8 "jessie" nut 2.7.2 slaves not
shutting down

On Wed, 18 Oct 2017, Drew Plaster wrote:
> ??????????????? there are three APC smart ups connected via usb cables 
> to the master system, the master system shuts down as expected but the 
> slave systems never shutdown eventhough I believe that all the configs 
> are properly set the slaves should either shutdown when there is only 
> one ups and it is running low on battery power offline or worst case 
> shutdown after they cannot communicate with the master for longer than 
> the HOSTSYNC 15 or UPS for longer than the DEADTIME 15
Hi, Could you show us your NUT configuration files?  Please omit the comments,
and double spacing will not be needed.

Roger
> Disclaimer: The information transmitted in this e-mail message and 
> attachments, if any, may contain confidential material, and is 
> intended only for the use of the individual or entity named above....
It's probably best not to send such a disclaimer to a public mailing list
with hundreds of subscribers.