On 3/28/26 9:30 PM, David C Rankin wrote:
Thank you Lukasz,
I'm a bit confused where it goes? It's an option to usbhid-ups
according to man upbhid-ups(8), but where in the config setup does it
go? The Arch wiki
(https://wiki.archlinux.org/title/Network_UPS_Tools#CyberPower_UPS_keeps_disconnecting/reconnecting)
talks about creating an override.conf, but it is unclear whether that
goes with [email protected] or nut-driver@valkyrie_ups.service.d?
The systemd targets and service files are a bit of a spiderweb:
I think that it is safer to alter nut-driver@valkyrie_ups.service. It is
autogenerated by enumerator from /etc/nut/ups.conf entries.
As for pollonly flag, it is an usbhid-ups config flag, so you have to
add it to your ups section in /etc/nut/ups.conf.
Picking up from the driver restart yesterday, the journal shows the
following:
The salient part starts with a spurious on-battery message and then
the connection with the UPS fails. I'm beginning to wonder if the
"on-battery" may not just be the daily self-test of the UPS, but then
why does it stop communicating with nut-monitor? It ran for 5+ years
with NUT 2.7 version and never had a disconnect issue, not one. Really
strange.
It looks like regression. Maybe some defaults for |pollfreq | or
|pollinterval |changed?
Regards,
Łukasz
