rPi3 running current Buster. I get this far:
# upsc networkups
Init SSL without certificate database
battery.charge: 100
battery.charge.warning: 30
battery.runtime: 2891
battery.type: PbAC
device.mfr: Vertiv Co
device.model: Liebert PST5
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 0002
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: Belkin/Liebert HID 0.17
driver.version.internal: 0.41
ups.mfr: Vertiv Co
ups.model: Liebert PST5
ups.productid: 0002
ups.serial:
ups.status: OL
ups.vendorid: 10af
when I run
# service nut-client start
I begin getting these:
Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:32:14 2020):
UPS networkups is unavailable
Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:36:44 2020):
Communications with UPS networkups established
Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:37:14 2020):
Communications with UPS networkups lost
Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:41:44 2020):
UPS networkups is unavailable
Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:47:14 2020):
UPS networkups is unavailable
When I originally set it up POLLFREQ and POLLFREQALERT were at 5 and
DEADTIME at 15 (defaults) and I started getting these soon after service
start. After a few increases I adjusted them to 30, 30 and 90 and it
took about 24 hours for the broadcasts to start. During my early
testing, when communications gots re-established automatically, the uspc
command worked, but otherwise I got "stale results" error. Restarting
the services (nut-server and nut-client) resolved the issue, only to
have the errors occur again.
FWIW, this rPi has an Adafruit Ultimate GPS Hat and is serving as a
stratum1 ntp server, as well as a secondary dns server.
Here is how I got here (post fresh rPi buster install and setting up ntp
and bind):
apt-get install nut nut-monitor nut-cgi nut-snmp snmp-mibs-downloader
added to /etc/udev/rules.d/62-nut-usbups.rules from /lib/udev/rules.d/
ATTR{idVendor}=="10af", ATTR{idProduct}=="0002",
MODE="664", GROUP="nut"
/etc/nut
nut.conf
MODE=standalone
ups.conf
[networkups]
driver = usbhid-ups
port = auto
desc = "Network Closet UPS"
productid = 0002
upsmon.conf
MONITOR networkups 1 upsmon pass master
POLLFREQ 30
POLLFREQALERT 30
DEADTIME 90
I've just set the POLLFREQ pair to 60 and DEADTIME to 180 and restarted
the nut-server and nut-client services. When I stopped them for this
config refresh I did NOT get any errors shutting the services down (and
I did stop/start not refresh). In my earlier testing I did get errors
about upsmon being dead when I tried to stop the server and client
(didn't doc that specifically, sorry). I'm not finding any log files,
but buster isn't my home; I'm old school Solaris migrating to illumos/OI
on on my server. Pointers to getting logging out of the services system
and pointers on fixing this would be most appreciated. I have a 2nd UPS
to add to the network so I have a ways to go.
--
joe
> On Sep 14, 2020, at 9:12 PM, Joe Reid <jreid at vnet.net> wrote: > > rPi3 running current Buster. I get this far: > > # upsc networkups > Init SSL without certificate database > battery.charge: 100 > battery.charge.warning: 30 > battery.runtime: 2891 > battery.type: PbAC > device.mfr: Vertiv Co > device.model: Liebert PST5 > device.type: ups > driver.name: usbhid-ups > driver.parameter.pollfreq: 30 > driver.parameter.pollinterval: 2 > driver.parameter.port: auto > driver.parameter.productid: 0002 > driver.parameter.synchronous: no > driver.version: 2.7.4 > driver.version.data: Belkin/Liebert HID 0.17 > driver.version.internal: 0.41 > ups.mfr: Vertiv Co > ups.model: Liebert PST5 > ups.productid: 0002 > ups.serial: > ups.status: OL > ups.vendorid: 10af > > when I run > # service nut-client start > I begin getting these: > Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:32:14 2020): > > UPS networkups is unavailable > > Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:36:44 2020): > > Communications with UPS networkups establishedAt this point, look to see what is running. I was doing 'ps auwwx | grep ups' On my system, which is attached to the UPS via a USB cable, I see: $ ps auwwx | grep ups uucp 49176 0.0 0.1 6636 2620 - Ss Sun18 6:11.49 /usr/local/libexec/nut/usbhid-ups -a ups02 root 64576 0.0 0.1 6464 2344 - Is Sun18 0:00.00 /usr/local/sbin/upsmon root 75485 0.0 0.1 6472 2396 - Ss Sun18 17:04.71 /usr/local/sbin/upsd -u root Do you see any of that?> > Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:37:14 2020): > > Communications with UPS networkups lost > > Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:41:44 2020): > > UPS networkups is unavailable > > Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:47:14 2020): > > UPS networkups is unavailableAt this point, are the processes you saw before still running? — Dan Langille http://langille <http://langille/>.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200919/ac267d4c/attachment.html>
On 9/19/2020 12:38 PM, Dan Langille wrote:>> On Sep 14, 2020, at 9:12 PM, Joe Reid <jreid at vnet.net >> <mailto:jreid at vnet.net>> wrote: >> >> rPi3 running current Buster. I get this far:...> I was doing 'ps auwwx | grep ups' > > On my system, which is attached to the UPS via a USB cable, I see: > > $ ps auwwx | grep ups > uucp 49176 0.0 0.1 6636 2620 - Ss Sun18 6:11.49 > /usr/local/libexec/nut/usbhid-ups -a ups02 > root 64576 0.0 0.1 6464 2344 - Is Sun18 0:00.00 > /usr/local/sbin/upsmon > root 75485 0.0 0.1 6472 2396 - Ss Sun18 17:04.71 > /usr/local/sbin/upsd -u root > > Do you see any of that?I am now and was I. I went a few days without any ability to talk to the UPS beyond lsusb and only now after a reboot of my rPi am I able to get upsd and upshid running Lots of unable to connect errors, even after disconnecting the usb connector and reconnecting. I did have on significant change, I used to get lots of info from the UPS when doing: # lsusb -vd 10af:0002 ... Report Descriptor: (length is 753) ... that returned a ton of data. I have a few lsusb where Report Descriptor length was returned as -7, and no data, and a timeout getting that, and now I get ** UNAVAILABLE ** for Report Descriptors and no data.>> Broadcast message from nut at nabhas (somewhere) (Mon Sep 14 17:47:14 >> 2020): >> >> UPS networkups is unavailable > > At this point, are the processes you saw before still running?Yes, the processes were running, it looked like upsmon had died and lost connection. I believe I saw errors to that affect. There is nothing else on the USB bus, but the other busses in the system aren't idle (gps hat tty data). I have also powered off and back on the UPS, and have also disconnected the USB cable from each end to no affect. I am concerned about the Report Descriptor data loss, am I looking at a faulty unit? -- joe