Found a way of addressing this without rebuilding nut. The following
restarts upsdrvctl when communications are lost (COMMBAD). I added NOCOMM
as a condition just in case. I've monitored this, and it successfully
reconnects when connection is lost.
Added to upsmon.conf
NOTIFYCMD /etc/nut/notify.sh
NOTIFYFLAG NOCOMM SYSLOG+WALL+EXEC
NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC
Then, /etc/nut/notify.sh is marked executable and contains:
#!/bin/bash
case "$NOTIFYTYPE" in
COMMBAD|NOCOMM)
/sbin/upsdrvctl stop;
/sbin/upsdrvctl start;
echo 'Restarted upsdrvctl' | systemd-cat -p notice -t upsd
;;
*) ;;
esac
On Tue, Aug 15, 2017 at 6:01 AM, Charles Lepple <clep...@gmail.com> wrote:
> On Aug 12, 2017, at 12:00 PM, Rory Jaffe <rsja...@gmail.com> wrote:
> >
> > OS Version: Linux piaware 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST
> 2017 armv7l GNU/Linux
> > Nut Version: 2.7.2-4
> > Nut Installation Method: apt
> > Device: CyberPower PR1500LCD
> > Uses Generic HID driver 0.38 (2.7.2)
>
> Is this stock Raspbian or another variant?
>
> If it is Raspbian, I think it might be affected by a Debian issue with
> libusb-0.1. It is possible to rebuild from source and use libusb-1.0
> instead - let us know if that sounds reasonable. You can also check the
> list archives for previous discussions (although I think we were seeing
> issues with Tripp-Lite hardware more frequently).
>
> Also, sometimes swapping out the USB cable can help.
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
