[Nut-upsuser] Tripplite SMART2200VS with tripplite_usb: UPS doesn't shut down

Wed May 25 19:43:21 UTC 2016

Please ignore the previous message as I sent it before it was complete.

Hello,

I have a Tripplite SMART2200VS that isn't being shut down when the nut
master asks it to.  My initial test was simply upsmon -c fsd which did
cause the system to shut down, however the UPS remained on and providing
power to its loads.  Looking in the logs (daemon and syslog) it was not
clear to me that NUT was actually telling the UPS to shut down (I was
expecting to see "Shutting down the UPS ..." in the logs based upon
/etc/init.d/nut-server).  Since I installed from packages rather than
source, and I could see the init scripts had support for the poweroff
command which calls upsdrvctl shutdown, I made the assumption that the
system is probably properly configured, but there may be a communication
issue with the UPS.  (may or may not be a logical assumption)

Next, I provided non-UPS power to the NUT master and shut down all the
loads connected to the UPS.  I then manually issued the shutdown via the
driver (/lib/nut/tripplite_usb -a tripplite -k -DDD) but the UPS still
remained up.  I don't know enough about NUT to debug this completely, but
my hunch is that the problem is with the communication between the driver
and the UPS, I'm just not clear on how to debug further.

Thanks for any additional assistance and insight!

--Larry

NUT master running on Raspberry Pi 3

# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

# uname -a
Linux pi 4.4.9-v7+ #884 SMP Fri May 6 17:28:59 BST 2016 armv7l GNU/Linux

# apt list nut* | grep installed
nut/stable,now 2.7.2-4 all [installed]
nut-client/stable,now 2.7.2-4 armhf [installed]
nut-server/stable,now 2.7.2-4 armhf [installed]

# tail -5 /etc/nut/ups.conf
[tripplite]
    driver = tripplite_usb
    port = auto
    desc = "Tripp Lite SMART2200VS"
    product = ".*SMART2200.*"

# /lib/nut/tripplite_usb -DDD -a tripplite
   0.000000     debug level is '3'
   0.003341     Checking device (09AE/0001) (001/004)
   0.014665     - VendorID: 09ae
   0.014721     - ProductID: 0001
   0.014760     - Manufacturer: TRIPP LITE
   0.014799     - Product: TRIPP LITE SMART2200VS
   0.014837     - Serial Number: unknown
   0.014874     - Bus: 001
   0.014911     Trying to match device
   0.015272     Device matches
   0.016162     Detected a UPS: TRIPP LITE/TRIPP LITE SMART2200VS
   0.016267     send_cmd(msg_len=2, type='
   0.117454     Using SMARTPRO protocol (3003)

# date; /lib/nut/tripplite_usb -a tripplite -k -DDD
Wed 25 May 12:51:12 CDT 2016
   0.000000     debug level is '3'
   0.003343     Checking device (09AE/0001) (001/004)
   0.014646     - VendorID: 09ae
   0.014680     - ProductID: 0001
   0.014698     - Manufacturer: TRIPP LITE
   0.014718     - Product: TRIPP LITE SMART2200VS
   0.014738     - Serial Number: unknown
   0.014755     - Bus: 001
   0.014771     Trying to match device
   0.015133     Device matches
   0.016020     Detected a UPS: TRIPP LITE/TRIPP LITE SMART2200VS
   0.016075     Initiating UPS shutdown
   0.016117     soft_shutdown(offdelay=64): N
   0.016137     send_cmd(msg_len=4, type='N')
   2.117586     send_cmd(msg_len=2, type='G')
   3.219418     libusb_get_interrupt: Connection timed out
   3.219474     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 47 b8 0d 00 00 00 00 '.G......'
   4.219593     libusb_get_interrupt: Connection timed out
   4.219661     libusb_get_interrupt() returned 0 instead of 8 while
sending 3a 47 b8 0d 00 00 00 00 '.G......'

The UPS never shut down.

Excerpts from the syslog from when I issued the upsmon -c fsd command:

May 24 18:01:57 pi upsmon[996]: Signal 10: User requested FSD
May 24 18:01:57 pi upsd[992]: Client upsmon at 127.0.0.1 set FSD on UPS
[tripplite]
May 24 18:01:57 pi upsmon[996]: Executing automatic power-fail shutdown
May 24 18:01:57 pi upsmon[996]: Auto logout and shutdown proceeding
May 24 18:02:01 pi CRON[2147]: (root) CMD (if test -x /usr/sbin/apticron;
then /usr/sbin/apticron --cron; else true; fi)
May 24 18:02:02 pi systemd[1]: Starting Delayed Shutdown Service...
May 24 18:02:02 pi systemd[1]: Started Delayed Shutdown Service.
May 24 18:02:02 pi systemd-shutdownd[2157]: Shutting down at Tue 2016-05-24
18:02:02 UTC (poweroff)...
May 24 18:02:02 pi systemd-shutdownd[2157]: Creating /run/nologin, blocking
further logins...
May 24 18:02:02 pi systemd[1]: Started Synchronise Hardware Clock to System
Clock.
May 24 18:02:02 pi systemd[1]: Started Turns off Raspberry Pi display
backlight on shutdown/reboot.
[...]
May 24 18:02:02 pi systemd[1]: Stopping Multi-User System.
May 24 18:02:02 pi systemd[1]: Stopped target Multi-User System.
May 24 18:02:02 pi systemd[1]: Stopping Regular background program
processing daemon...
May 24 18:02:02 pi systemd[1]: Stopping OpenBSD Secure Shell server...
May 24 18:02:02 pi systemd[1]: Stopping Network UPS Tools - power devices
information server...
May 24 18:02:02 pi systemd[1]: Service nut-driver.service is not needed
anymore. Stopping.
May 24 18:02:02 pi systemd[1]: Stopping Login Prompts.
May 24 18:02:02 pi systemd[1]: Stopped target Login Prompts.
May 24 18:02:02 pi systemd[1]: Stopping Getty on tty1...
May 24 18:02:02 pi systemd[1]: Stopping Login Service...
May 24 18:02:02 pi systemd[1]: Stopping LSB: exim Mail Transport Agent...
May 24 18:02:02 pi bluetoothd[592]: Terminating
May 24 18:02:02 pi bluetoothd[592]: Stopping SDP server
May 24 18:02:02 pi bluetoothd[592]: Exit
May 24 18:02:02 pi upsd[992]: mainloop: Interrupted system call
May 24 18:02:02 pi upsd[992]: Signal 15: exiting

-- 
Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com
           Minneapolis, Minnesota       www.FahnoeTech.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160525/f4a33f32/attachment-0001.html>