Communications lost, communications established
-
@dennypage About once per hour, pfSense NUT kicks out a message:
"Communications with UPS TrippLiteSU1000RTXLCD2U lost"
followed by "UPS TrippLiteSU1000RTXLCD2U is unavailable"
followed by "Communications with UPS TrippLiteSU1000RTXLCD2U established"
All three of these messages come in the space of one minute.
This didn't happen before I upgraded to pfSense 2.7 and NUT 2.8.2_1. I had years of trouble free operation.
What is the source of this instability (or high notification rate)? I have added the quirk as per the message above.
PS. Also, please note that I'm hoping to get answers to my previous quiestions about user=root, USB bus 0, etc.
-
@serengeti Most likely thing is that you were experiencing disconnects previously and it wasn't being logged.
I suggest running the driver with debug to see whether the issue is the UPS disappearing from USB, or some form of protocol error.
-
@dennypage I still am having issues with notifications flooding in...
Communications with UPS ups lost
Communications with UPS ups established
every couple of minutes when enabling notifications. btw, I run Pfsense on a Protectli Vault FW2B - 2 Port which is running an intel processor. my ups is an old apc sua2200 connected with a usb cable. it's the old style rj45 to usb cable. as you can see, I haven't added any driver configuration lines and wonder if I should.
-
@Cloudless-Smart-Home Please see post above.
-
@dennypage I don't know how. looked at the nut driver manual page and there was no mention of debug. I do see DEBUG_MIN INTEGER for UPSMON.CONF. is this what you are referring to? if so, what level then?
thanks
-
First start the service, and then kill the driver:
killall usbhid-upsThen, run the driver with debug:
/usr/local/libexec/nut/usbhid-ups -DDD -a YOUR_UPS_NAME_HERESee what error it shows. If it doesn't show enough you can add more 'D's until it does up to "-DDDDDD".
-
@dennypage does this help?
ups troubleshooting.txt
