Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Lane Russell]

​I will try the PPA next; however, I have been monitoring things for
several weeks now with no issues. I'm trying to figure out if there was a
package update somewhere that calmed things down.​

On Sun, Oct 30, 2016 at 9:56 AM, Charles Lepple  wrote:

> I finally got the PPA updated:
>
> https://launchpad.net/~clepple/+archive/ubuntu/nut
>
> The latest version there was built with libusb-1.0 instead of libusb-0.1.
> I still get the occasional issue with the Tripp Lite 3016 device with this
> code, but it seems to be less frequent. I will need to swap around some
> equipment to be able to test against a CyberPower UPS (mine isn't an LCD
> model, though).
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Charles Lepple]

I finally got the PPA updated:

https://launchpad.net/~clepple/+archive/ubuntu/nut

The latest version there was built with libusb-1.0 instead of libusb-0.1. I 
still get the occasional issue with the Tripp Lite 3016 device with this code, 
but it seems to be less frequent. I will need to swap around some equipment to 
be able to test against a CyberPower UPS (mine isn't an LCD model, though).
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Lane Russell]

There's no GUI here; NUT Is running on a headless server. There is only one
usbhid-ups process running:

nut  13710  0.0  0.0  17320   344 ?Ss   Oct21   0:18
/lib/nut/usbhid-ups -a ups

On Mon, Oct 24, 2016 at 6:11 PM, Charles Lepple  wrote:

> On Oct 24, 2016, at 10:38 AM, Lane Russell 
> wrote:
> >
> > How could I check if another instance is causing me issues? This is a
> running on a KVM host server, so there's very little activity on the server
> itself.
>
> There should only be one usbhid-ups process running at any given time.
> Also, from your description, this does not sound likely, but was there a
> GUI login at the time corresponding to that error? (I realize this might be
> annoying to deduce from the relative timestamps that NUT provides.)
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Charles Lepple]

On Oct 24, 2016, at 10:38 AM, Lane Russell  wrote:
> 
> How could I check if another instance is causing me issues? This is a running 
> on a KVM host server, so there's very little activity on the server itself. 

There should only be one usbhid-ups process running at any given time. Also, 
from your description, this does not sound likely, but was there a GUI login at 
the time corresponding to that error? (I realize this might be annoying to 
deduce from the relative timestamps that NUT provides.)
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Lane Russell]

How could I check if another instance is causing me issues? This is a
running on a KVM host server, so there's very little activity on the server
itself.

On Sat, Oct 22, 2016 at 1:16 PM, Charles Lepple  wrote:

> No, just a few extra hours in the day :)
>
> This is a tougher problem.
>
> In the mean time, can you make sure the "Got disconnected by another
> driver " is not really caused by an extra instance of the NUT driver?
> (Could be kernel or other user space activity)
>
> - Charles
>
> On Oct 21, 2016, at 11:37 AM, Lane Russell 
> wrote:
>
> Do you need any more info from me on this?
>
> On Fri, Oct 14, 2016 at 7:56 AM, Lane Russell 
> wrote:
>
>> ​Increasing 'pollinterval' to 5s did not seem to work. I've attached the
>> relevant portions of the upsdrvctl debug. I believe the message we're
>> looking at is:
>>
>> 9528.632309 libusb_get_report: error sending control message: Device or
>> resource busy
>> 9528.632318 Can't retrieve Report 16: Device or resource busy
>> 9528.632326 Got disconnected by another driver: Device or resource busy​
>>
>> On Wed, Oct 12, 2016 at 8:35 AM, Charles Lepple 
>> wrote:
>>
>>> On Oct 12, 2016, at 9:07 AM, Lane Russell wrote:
>>> >
>>> > Apologies, I did mean upsmon.conf. ups.conf "pollinterval" is not
>>> called out, so I assume it's using the default of 2s. "pollfreq" and
>>> "pollfreqalert" are both set to 10s in upsmon.conf at the moment.
>>> "deadtime" is set to 30s.
>>>
>>> No problem, the names are a bit confusing.
>>>
>>> > I've attached the output of "sudo /lib/nut/usbhid-ups -a ups -DDD".
>>>
>>> I forgot to mention, the list limits messages to ~40 KB, so for the next
>>> time, please compress the log ("gzip -9" or similar).
>>>
>>> However, we would need the log at the point where the UPS disconnects.
>>> (The beginning looks normal.) If the compressed log is still large, let me
>>> know and we can trim out the interesting part.
>>>
>>> > Forgive me, but I've never rebuilt a driver, and I'm not sure what the
>>> libusb branch is. Could you elaborate? Or perhaps this issue won't be
>>> related to that and we won't have to go down that path.
>>>
>>> There are still a few things to try before then, and they are somewhat
>>> related to what the log looks like at the point when the driver declares
>>> the data stale.
>>>
>>> Also, maybe I can get things set up again to build packages for an
>>> Ubuntu PPA.
>>
>>
>>
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Charles Lepple]

No, just a few extra hours in the day :)

This is a tougher problem.

In the mean time, can you make sure the "Got disconnected by another driver " 
is not really caused by an extra instance of the NUT driver? (Could be kernel 
or other user space activity)

- Charles

> On Oct 21, 2016, at 11:37 AM, Lane Russell  wrote:
> 
> Do you need any more info from me on this?
> 
>> On Fri, Oct 14, 2016 at 7:56 AM, Lane Russell  
>> wrote:
>> ​Increasing 'pollinterval' to 5s did not seem to work. I've attached the 
>> relevant portions of the upsdrvctl debug. I believe the message we're 
>> looking at is:
>> 
>> 9528.632309  libusb_get_report: error sending control message: Device or 
>> resource busy
>> 9528.632318  Can't retrieve Report 16: Device or resource busy
>> 9528.632326  Got disconnected by another driver: Device or resource busy​
>> 
>>> On Wed, Oct 12, 2016 at 8:35 AM, Charles Lepple  wrote:
>>> On Oct 12, 2016, at 9:07 AM, Lane Russell wrote:
>>> >
>>> > Apologies, I did mean upsmon.conf. ups.conf "pollinterval" is not called 
>>> > out, so I assume it's using the default of 2s. "pollfreq" and 
>>> > "pollfreqalert" are both set to 10s in upsmon.conf at the moment. 
>>> > "deadtime" is set to 30s.
>>> 
>>> No problem, the names are a bit confusing.
>>> 
>>> > I've attached the output of "sudo /lib/nut/usbhid-ups -a ups -DDD".
>>> 
>>> I forgot to mention, the list limits messages to ~40 KB, so for the next 
>>> time, please compress the log ("gzip -9" or similar).
>>> 
>>> However, we would need the log at the point where the UPS disconnects. (The 
>>> beginning looks normal.) If the compressed log is still large, let me know 
>>> and we can trim out the interesting part.
>>> 
>>> > Forgive me, but I've never rebuilt a driver, and I'm not sure what the 
>>> > libusb branch is. Could you elaborate? Or perhaps this issue won't be 
>>> > related to that and we won't have to go down that path.
>>> 
>>> There are still a few things to try before then, and they are somewhat 
>>> related to what the log looks like at the point when the driver declares 
>>> the data stale.
>>> 
>>> Also, maybe I can get things set up again to build packages for an Ubuntu 
>>> PPA.
>> 
> 
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Lane Russell]

​Increasing 'pollinterval' to 5s did not seem to work. I've attached the
relevant portions of the upsdrvctl debug. I believe the message we're
looking at is:

9528.632309 libusb_get_report: error sending control message: Device or
resource busy
9528.632318 Can't retrieve Report 16: Device or resource busy
9528.632326 Got disconnected by another driver: Device or resource busy​

On Wed, Oct 12, 2016 at 8:35 AM, Charles Lepple  wrote:

> On Oct 12, 2016, at 9:07 AM, Lane Russell wrote:
> >
> > Apologies, I did mean upsmon.conf. ups.conf "pollinterval" is not called
> out, so I assume it's using the default of 2s. "pollfreq" and
> "pollfreqalert" are both set to 10s in upsmon.conf at the moment.
> "deadtime" is set to 30s.
>
> No problem, the names are a bit confusing.
>
> > I've attached the output of "sudo /lib/nut/usbhid-ups -a ups -DDD".
>
> I forgot to mention, the list limits messages to ~40 KB, so for the next
> time, please compress the log ("gzip -9" or similar).
>
> However, we would need the log at the point where the UPS disconnects.
> (The beginning looks normal.) If the compressed log is still large, let me
> know and we can trim out the interesting part.
>
> > Forgive me, but I've never rebuilt a driver, and I'm not sure what the
> libusb branch is. Could you elaborate? Or perhaps this issue won't be
> related to that and we won't have to go down that path.
>
> There are still a few things to try before then, and they are somewhat
> related to what the log looks like at the point when the driver declares
> the data stale.
>
> Also, maybe I can get things set up again to build packages for an Ubuntu
> PPA.


upsdrvctl_redacted.tar.gz
Description: GNU Zip compressed data
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Charles Lepple]

On Oct 12, 2016, at 9:07 AM, Lane Russell wrote:
> 
> Apologies, I did mean upsmon.conf. ups.conf "pollinterval" is not called out, 
> so I assume it's using the default of 2s. "pollfreq" and "pollfreqalert" are 
> both set to 10s in upsmon.conf at the moment. "deadtime" is set to 30s.

No problem, the names are a bit confusing.

> I've attached the output of "sudo /lib/nut/usbhid-ups -a ups -DDD".

I forgot to mention, the list limits messages to ~40 KB, so for the next time, 
please compress the log ("gzip -9" or similar).

However, we would need the log at the point where the UPS disconnects. (The 
beginning looks normal.) If the compressed log is still large, let me know and 
we can trim out the interesting part.

> Forgive me, but I've never rebuilt a driver, and I'm not sure what the libusb 
> branch is. Could you elaborate? Or perhaps this issue won't be related to 
> that and we won't have to go down that path.

There are still a few things to try before then, and they are somewhat related 
to what the log looks like at the point when the driver declares the data stale.

Also, maybe I can get things set up again to build packages for an Ubuntu PPA.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Charles Lepple]

On Oct 10, 2016, at 11:32 PM, Lane Russell wrote:
> 
> It looks like I'm currently on 4.4.0-38
> 
> uname -a:
> Linux kvm 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 
> x86_64 x86_64 GNU/Linux

Ah, right, the default kernel for Ubuntu 16.04. (I am getting the distributions 
mixed up.)

Can you try the libusb-1.0 branch? It's possible to configure NUT using the 
same options as for the .deb package, so you would only need to rebuild the one 
usbhid-ups driver.

Also, you mentioned "Reducing POLLFREQ & POLLFREQALERT from 5s to 10s". The 
default value for "pollfreq" in ups.conf is 30 seconds. If you are referring to 
the POLLFREQ option in upsmon.conf, it does need to be greater than 
"pollinterval", but you can raise them both.

The symptom of having the driver poll the UPS too frequently (as set in 
ups.conf) is that the driver might overload the USB microcontroller in the UPS, 
and could cause the UPS to disconnect (as Stuart mentioned for his Tripp Lite 
UPS). If upsmon polls faster than the driver, then you will also get "data 
stale" messages, but that is unfortunately not a unique symptom - hence the 
need for more detailed logs.

It looks like your version of "upsdrvctl" doesn't pass "-D" to the driver. For 
Ubuntu, you can start the driver directly like so:

/lib/nut/usbhid-ups -a ups -DDD
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM - a bit offtopic as it's about SSL certificates

[Manuel Wolfshant]

On 10/11/2016 12:00 AM, Mark Hansen wrote:

If you want to avoid this, you need to purchase a certificate signed by a
well-known CA and install that on your server.


actually the free certificates issued by several companies, starting 
with letsencrypt and startssl.com(*), are just fine when installed 
properly ( i.e. including all the CA and issuer certificates as well, 
not just the server )



(*) I used to use startssl's certs but I quit this very month given that 
they were acquired by a shady Chinese company. the topic exceeds the 
scope of this list so I will not provide details here but 
http://www.percya.com/2016/09/wosigns-secret-purchase-of-startcom.html 
(and the links pointed out by this article) + 
http://www.theregister.co.uk/2016/09/27/mozilla_wants_woeful_wosign_certs_off_the_list/ 
provide enough info for an educated decision



___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Lane Russell]

It looks like I'm currently on 4.4.0-38

uname -a:
Linux kvm 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux

On Mon, Oct 10, 2016 at 10:04 PM, Charles Lepple  wrote:

>
> On Oct 6, 2016, at 7:26 PM, Lane Russell  wrote:
>
> Ubuntu Server 16.04.1 LTS
> NUT 2.7.2-4ubuntu1
>
> Apologies if you mentioned this already, but which kernel are you running?
>
> Looking back over the recent USB problems, we saw a lot of problems with
> the 3.16 kernel, for instance.
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Charles Lepple]

> On Oct 6, 2016, at 7:26 PM, Lane Russell  wrote:
> 
> Ubuntu Server 16.04.1 LTS
> NUT 2.7.2-4ubuntu1
> 
Apologies if you mentioned this already, but which kernel are you running?

Looking back over the recent USB problems, we saw a lot of problems with the 
3.16 kernel, for instance.___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM [DNS]

[Stuart Gathman]

On 10/10/2016 07:49 PM, Charles Lepple wrote:
> Google's 8.8.8.8 DNS returns the following:
>
> $ host gathman.org
> gathman.org has address 70.184.247.44
> gathman.org has IPv6 address 2001:470:8:809::1010
>
> I'm getting a 404 using the IPv4 address. Is it possible that Lane's phone 
> was using IPv6 when it worked?

Ah yes.  I keep forgetting people are still using IP4.  I natted that
IP4 to the public server, and tested from NYC with ipv4 forced.


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM [DNS]

[Charles Lepple]

> On Oct 10, 2016, at 2:12 PM, Stuart D. Gathman  wrote:
> 
> On Mon, 10 Oct 2016, Lane Russell wrote:
> 
>> I tried viewing your link, but it returns a 404 error. It also doesn't seem
>> to have a valid certificate. Could you send the correct link please?
> 
> I tried from Texas, Miami, Virginia, and New York VPSes. Works fine.
> Maybe try again, or check your local DNS?

Google's 8.8.8.8 DNS returns the following:

$ host gathman.org
gathman.org has address 70.184.247.44
gathman.org has IPv6 address 2001:470:8:809::1010

I'm getting a 404 using the IPv4 address. Is it possible that Lane's phone was 
using IPv6 when it worked?
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Mark Hansen]

On 10/10/2016 11:12 AM, Stuart D. Gathman wrote:

On Mon, 10 Oct 2016, Lane Russell wrote:


I tried viewing your link, but it returns a 404 error. It also doesn't seem
to have a valid certificate. Could you send the correct link please?


I tried from Texas, Miami, Virginia, and New York VPSes. Works fine.
Maybe try again, or check your local DNS?


I was able to get it to run unattended with this hack:
https://gathman.org/2016/07/30/Standard_Schmandard/




Stuart,

The issue is the certificate presented by your server (gathman.org) is not
signed by a well-known CA. Also, it looks like the certificate is valid only
for fairfax.gathman.org, while the URL you provided is to gathman.org.

Because of this, normal browsers will complain about the certificate unless
the user creates an "exception" (installs your certificate locally and
authorizes it for use when contacting your web site).

If you want to avoid this, you need to purchase a certificate signed by a
well-known CA and install that on your server.

If you don't want to do that, just be aware that anyone connecting to your
server is going to get a similar error.

Note that *you* don't get this error probably because you've installed
an exception for your certificate to your local browser. No matter what
path you take to get to the server, your browser will accept the certificate
and display the site without the warning.

As an alternative, you can offer the non-SSL URL to the content, if your
server allows for such access. This won't require the use of a certificate.


FYI.


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Stuart D. Gathman]

On Mon, 10 Oct 2016, Lane Russell wrote:


I tried viewing your link, but it returns a 404 error. It also doesn't seem
to have a valid certificate. Could you send the correct link please?


I tried from Texas, Miami, Virginia, and New York VPSes. Works fine.
Maybe try again, or check your local DNS?


I was able to get it to run unattended with this hack:
https://gathman.org/2016/07/30/Standard_Schmandard/


--
  Stuart D. Gathman 
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Lane Russell]

Huh, must be an OpenDNS issue, it works from my phone. 

I wonder if I'm running into a similar defect on the PC UPS... I could try 
resetting the driver every few hours (this, in addition to replugging the cable 
fixes the issue temporarily), but that does feel like a hack that doesn't fix 
the root cause.

I will try returning the unit and give APC a go. I've previously had good luck 
with one of their older units. I'll update here as to whether that fixes my 
issue.

On October 10, 2016 1:12:01 PM CDT, "Stuart D. Gathman"  
wrote:
>On Mon, 10 Oct 2016, Lane Russell wrote:
>
>> I tried viewing your link, but it returns a 404 error. It also
>doesn't seem
>> to have a valid certificate. Could you send the correct link please?
>
>I tried from Texas, Miami, Virginia, and New York VPSes. Works fine.
>Maybe try again, or check your local DNS?
>
>> I was able to get it to run unattended with this hack:
>> https://gathman.org/2016/07/30/Standard_Schmandard/
>
>-- 
> Stuart D. Gathman 
>"Confutatis maledictis, flamis acribus addictis" - background song for
>a Microsoft sponsored "Where do you want to go from here?" commercial.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Lane Russell]

I tried viewing your link, but it returns a 404 error. It also doesn't seem
to have a valid certificate. Could you send the correct link please?

On Thu, Oct 6, 2016 at 9:14 PM, Stuart Gathman  wrote:

> On 10/06/2016 07:26 PM, Lane Russell wrote:
>
> ​​
> Syslog after server loses sight of UPS:
> Oct  6 17:29:01 kvm usbhid-ups[3529]: libusb_get_string: error sending
> control message: Broken pipe
> Oct  6 17:30:53 kvm upsd[3533]: Data for UPS [ups] is stale - check driver
> Oct  6 17:30:57 kvm upsmon[3548]: Poll UPS [ups@localhost] failed - Data
> stale
> Oct  6 17:30:57 kvm upsmon[3548]: Communications with UPS ups@localhost
> lost
> Oct  6 17:30:57 kvm upssched[32410]: Executing command: notifycommbad
>
> My Tripplight SMART1500LCDT
> 
> has the same problem, with the above preceded by:
>
> Oct  2 22:20:02 fairfax kernel: hub 1-1.1.1:1.0: port 4 disabled by hub
> (EMI?), re-enabling...
> Oct  2 22:20:02 fairfax kernel: usb 1-1.1.1.4: USB disconnect, device
> number 19
> Oct  2 22:20:04 fairfax nagios: HOST ALERT: h.dvorak;DOWN;SOFT;1;(Host
> Check Timed Out)
> Oct  2 22:20:06 fairfax kernel: hub 1-1.1.1:1.0: Cannot enable port 4.
> Maybe the USB cable is bad?
> Oct  2 22:20:10 fairfax kernel: hub 1-1.1.1:1.0: Cannot enable port 4.
> Maybe the USB cable is bad?
> Oct  2 22:20:14 fairfax kernel: hub 1-1.1.1:1.0: Cannot enable port 4.
> Maybe the USB cable is bad?
> Oct  2 22:20:17 fairfax kernel: hub 1-1.1.1:1.0: Cannot enable port 4.
> Maybe the USB cable is bad?
> Oct  2 22:20:17 fairfax kernel: hub 1-1.1.1:1.0: unable to enumerate USB
> device on port 4
>
> I was able to get it to run unattended with this hack:
> https://gathman.org/2016/07/30/Standard_Schmandard/
>
> ___
> Nut-upsuser mailing list
> Nut-upsuser@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

[Stuart Gathman]

On 10/06/2016 07:26 PM, Lane Russell wrote:
> ​​
> Syslog after server loses sight of UPS:
> Oct  6 17:29:01 kvm usbhid-ups[3529]: libusb_get_string: error sending
> control message: Broken pipe
> Oct  6 17:30:53 kvm upsd[3533]: Data for UPS [ups] is stale - check driver
> Oct  6 17:30:57 kvm upsmon[3548]: Poll UPS [ups@localhost] failed -
> Data stale
> Oct  6 17:30:57 kvm upsmon[3548]: Communications with UPS
> ups@localhost lost
> Oct  6 17:30:57 kvm upssched[32410]: Executing command: notifycommbad
My Tripplight SMART1500LCDT

has the same problem, with the above preceded by:

Oct  2 22:20:02 fairfax kernel: hub 1-1.1.1:1.0: port 4 disabled by hub
(EMI?), re-enabling...
Oct  2 22:20:02 fairfax kernel: usb 1-1.1.1.4: USB disconnect, device
number 19
Oct  2 22:20:04 fairfax nagios: HOST ALERT: h.dvorak;DOWN;SOFT;1;(Host
Check Timed Out)
Oct  2 22:20:06 fairfax kernel: hub 1-1.1.1:1.0: Cannot enable port 4. 
Maybe the USB cable is bad?
Oct  2 22:20:10 fairfax kernel: hub 1-1.1.1:1.0: Cannot enable port 4. 
Maybe the USB cable is bad?
Oct  2 22:20:14 fairfax kernel: hub 1-1.1.1:1.0: Cannot enable port 4. 
Maybe the USB cable is bad?
Oct  2 22:20:17 fairfax kernel: hub 1-1.1.1:1.0: Cannot enable port 4. 
Maybe the USB cable is bad?
Oct  2 22:20:17 fairfax kernel: hub 1-1.1.1:1.0: unable to enumerate USB
device on port 4

I was able to get it to run unattended with this hack:
https://gathman.org/2016/07/30/Standard_Schmandard/
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] CP1500AVRLCD NOCOMM

[Lane Russell]

​​
Ubuntu Server 16.04.1 LTS
NUT 2.7.2-4ubuntu1
NUT installed from apt
CP1500AVRLCDa
Complete problem description, with any relevant traces, like system log
excerpts, and driver debug output. You can obtain the latter using the
following command, as root and after having stopped NUT:

Problem Description:
Ubuntu is able to communicate fine with the ups for several hours. However,
the UPS is consistently going stale after a few hours. At that point, I
have either manually reconnect the cable, or restart the driver. Both fix
the issue for a few hours, but the cycle repeats.

Things I have tried:
Different USB cable
Different USB port on server
Reducing POLLFREQ & POLLFREQALERT from 5s to 10s

Output of sudo upsdrvctl -D start:
Network UPS Tools - UPS driver controller 2.7.2
  0.00 Starting UPS: ups
Network UPS Tools - Generic HID driver 0.38 (2.7.2)
USB communication driver 0.32
Using subdriver: CyberPower HID 0.3


Syslog after server loses sight of UPS:
Oct  6 17:29:01 kvm usbhid-ups[3529]: libusb_get_string: error sending
control message: Broken pipe
Oct  6 17:30:53 kvm upsd[3533]: Data for UPS [ups] is stale - check driver
Oct  6 17:30:57 kvm upsmon[3548]: Poll UPS [ups@localhost] failed - Data
stale
Oct  6 17:30:57 kvm upsmon[3548]: Communications with UPS ups@localhost lost
Oct  6 17:30:57 kvm upssched[32410]: Executing command: notifycommbad
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser