Re: [Nut-upsuser] usbhid-ups: Failed to open device, skipping. (Permission denied)

2017-04-09 Thread Stuart Gathman 
On 04/08/2017 08:08 AM, Sam Varshavchik wrote:
> Stuart Gathman writes:
>
>>
>> I also had this problem with this unit.  My hacky solution solution is
>> here: https://github.com/sdgathman/trippfix
> What would be the symptoms of this that I would be seeing? I don't see
> anything in syslog, only usbhid-ups getting a periodic timeout, but
> each time it successfully reconnects via USB.
The main symptom in my unit is that the UPS drops off the USB bus
entirely, not responding in any way, not even rebooting the host helps. 
However, unplugging the USB cable resets the USB interface on the UPS,
and it then starts working again for some random number of days.   My
work around lets the host reset the UPS by removing power from the port
- electronically unplugging the USB cable.

>
> It is not entirely unprecedented for manufacturers to quitely fix
> defects in their hardware, then simply continue to ship it as the same
> model. It's been about a week since this unit has been plugged in,
> with the only issue being these usbhid-ups timeouts, which it now
> apparently recovers from it.
You know it.  It's especially annoying when they use a completely
different chipset on a USB device, and expect it to be no problem
because it ships with new Windows drivers...





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

Re: [Nut-upsuser] usbhid-ups: Failed to open device, skipping. (Permission denied)

2017-04-08 Thread Sam Varshavchik 

Stuart Gathman writes:


On 04/07/2017 09:15 PM, Sam Varshavchik wrote:
> Charles Lepple writes:
>
>>
>> Full gory details here: https://github.com/networkupstools/nut/pull/122
>
> This particular new unit came with its own USB cable, and this unit is
> plugged into a relatively old server. The motherboard is about ten
> years old.
>
I also had this problem with this unit.  My hacky solution solution is
here: https://github.com/sdgathman/trippfix

I'm convinced that the USB interface on these units is braindead -
despite their other excellent qualities (excellent handling of
outages).  Many other people have the same problem with this unit,
including Windows users with the supplied proprietary monitoring
software, so I think it is hardware.


What would be the symptoms of this that I would be seeing? I don't see  
anything in syslog, only usbhid-ups getting a periodic timeout, but each  
time it successfully reconnects via USB.


It is not entirely unprecedented for manufacturers to quitely fix defects in  
their hardware, then simply continue to ship it as the same model. It's been  
about a week since this unit has been plugged in, with the only issue being  
these usbhid-ups timeouts, which it now apparently recovers from it.





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

Re: [Nut-upsuser] usbhid-ups: Failed to open device, skipping. (Permission denied)

2017-04-07 Thread Stuart Gathman 
On 04/07/2017 09:15 PM, Sam Varshavchik wrote:
> Charles Lepple writes:
>
>>
>> Full gory details here: https://github.com/networkupstools/nut/pull/122
>
> This particular new unit came with its own USB cable, and this unit is
> plugged into a relatively old server. The motherboard is about ten
> years old.
>
I also had this problem with this unit.  My hacky solution solution is
here: https://github.com/sdgathman/trippfix

I'm convinced that the USB interface on these units is braindead -
despite their other excellent qualities (excellent handling of
outages).  Many other people have the same problem with this unit,
including Windows users with the supplied proprietary monitoring
software, so I think it is hardware.



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

Re: [Nut-upsuser] usbhid-ups: Failed to open device, skipping. (Permission denied)

2017-04-07 Thread Charles Lepple 
On Sun, Apr 2, 2017 at 2:59 AM, Sam Varshavchik  wrote:
> Having trouble configuring nut 2.7.4 on Fedora 25, with a new Tripp Lite
> UPS.
>
> I'm running XFCE, and XFCE's Power Manager sees the UPS just fine. lsusb
> gives:
>
> Bus 006 Device 002: ID 09ae:3016 Tripp Lite

I'm still catching up on mail, so apologies if this was covered on a
more recent GitHub issue, but Tripp Lite PID 3016 is extra-sensitive
to certain combinations of USB cables and newer motherboards. If you
take NUT and XFCE power manager out of the equation, but the UPS still
generates a lot of disconnect/timeout/reconnect traffic in the kernel
logs, you might be up against this issue.

Full gory details here: https://github.com/networkupstools/nut/pull/122

-- 
- Charles Lepple

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

[Nut-upsuser] usbhid-ups: Failed to open device, skipping. (Permission denied)

2017-04-01 Thread Sam Varshavchik 
Having trouble configuring nut 2.7.4 on Fedora 25, with a new Tripp Lite  
UPS.


I'm running XFCE, and XFCE's Power Manager sees the UPS just fine. lsusb  
gives:


Bus 006 Device 002: ID 09ae:3016 Tripp Lite

nut-scanner -U has no issues either:

# nut-scanner -U
Scanning USB bus.
[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "09AE"
productid = "3016"
product = "TRIPP LITE UPS"
serial = "2643FVLSM871900817"
vendor = "Tripp Lite"
bus = "006"

I took this and placed it in ups.conf, but upsdrvctl fails to start.  
Following the bread crumbs, I arrived at:


# /usr/sbin/usbhid-ups -D -D -D -a nutdev1

...

  0.054668  Checking device (09AE/3016) (006/002)
  0.054764  Failed to open device, skipping. (Permission denied)


Running this with strace I see this:

write(2, "Checking device (09AE/3016) (006/002)\n", 38) = 38
open("/dev/bus/usb/006/002", O_RDWR)= -1 EACCES (Permission denied)
write(2, "   0.054764\t", 12)   = 12
write(2, "Failed to open device, skipping. (Permission denied)\n", 53) = 53
write(2, "   0.054830\t", 12)   = 12

Can't open the USB device. I have SELinux set to permissive, so this isn't  
the issue.





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