[Nut-upsuser] Question on EATON UPS

[laurenttaieb at free.fr]

I’m making some progress I believe…

I switched off and switched on the UPS further to the laptop having started the daemon and I’m not getting the same error message which is probably due to the server working in the background still locking the device

I think the daemon starts but gets into an infinite loop and doesn’t finish and hand back control.

Here are the updated traces I got by restarting : sudo ./usbhid-ups -a myups3 -DDD>& tracefile

Please apologies for the extra length of the traces as most of them are probably irrelevant (I had to cut the main file into multiple chunks):

 

I have zipped the trace as requested.

Thanks

Laurent

 

De : Nut-upsuser <nut-upsuser-bounces+laurenttaieb=free.fr at alioth-lists.debian.net <mailto:nut-upsuser-bounces+laurenttaieb=free.fr at alioth-lists.debian.net> > au nom de Laurent Taieb via Nut-upsuser <nut-upsuser at alioth-lists.debian.net <mailto:nut-upsuser at alioth-lists.debian.net> >
Répondre à : "laurenttaieb at free.fr <mailto:laurenttaieb at free.fr> " <laurenttaieb at free.fr <mailto:laurenttaieb at free.fr> >
Date : samedi 25 mars 2023 à 11:18
À : Jim Klimov <jimklimov+nut at gmail.com <mailto:jimklimov+nut at gmail.com> >
Cc : nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org <mailto:nut-upsuser at lists.alioth.debian.org> >
Objet : Re: [Nut-upsuser] Question on EATON UPS

 

No I’m not.

I’ll try to reboot the laptop and check if the daemon will generate more meaningful traces.
Thanks

Laurent 

 

Le 25 mars 2023 à 09:13, Jim Klimov <jimklimov+nut at gmail.com <mailto:jimklimov+nut at gmail.com> > a écrit :



Also, just in case - are you in  a virtualized environment? Is there (intentional or not) USB pass-through to the UPSes? My hint is, we had cases where a host or guest grabbed the device but it was not apparent from the part of system running NUT.

 

Jim

 

On Fri, Mar 24, 2023, 23:23 Jim Klimov <jimklimov+nut at gmail.com <mailto:jimklimov%2Bnut at gmail.com> > wrote:

Sounds like some other program is holding the port. Have you stopped other NUT drivers for the device (e.g. via auto-resuscitating services) before starting this one? Does udev, ugen or similar facility have the configuration to hand off this device to NUT run-time user? (BTW, if you are now testing a custom build - was it configured to use same accounts as pre-packaged variant)?

 

On Fri, Mar 24, 2023, 18:46 Laurent Taieb <laurenttaieb at free.fr <mailto:laurenttaieb at free.fr> > wrote:

Hi Jim,

I have 2 drivers which have launched well connecting 2 APC UPS (both with usbhid-ups)

They have both bus & serial set.

The Eaton is the third one. I have removed serial and bus from the configuration.

 

                driver : usbhid-ups

                port = auto

                vendorid = 0463

                productid = ffff

                pollonly

 

I have highlighted the errors while launching the driver: 

 

0.039057             [D2] Checking device 4 of 10 (214B/7250)

   0.039099         [D1] Failed to open device (214B/7250), skipping: Access denied (insufficient permissions)

   0.039109         [D2] Checking device 5 of 10 (0463/FFFF)

  0.956144         [D1] nut_libusb_open get iManufacturer failed, retrying...

   0.956518         [D1] nut_libusb_open get iManufacturer failed, retrying...

   0.956836         [D1] nut_libusb_open get iManufacturer failed, retrying...

   0.957291         [D1] nut_libusb_open get iProduct failed, retrying...

   0.957708         [D1] nut_libusb_open get iProduct failed, retrying...

   0.958098         [D1] nut_libusb_open get iProduct failed, retrying...

   0.958135         [D2] - VendorID: 0463

   0.958184         [D2] - ProductID: ffff

   0.958207         [D2] - Manufacturer: unknown

   0.958254         [D2] - Product: unknown

   0.958274         [D2] - Serial Number: unknown

   0.958297         [D2] - Bus: 002

   0.958372         [D2] - Device: unknown

   0.958391         [D2] - Device release number: 0001

   0.958432         [D2] Trying to match device

   0.958475         [D2] match_function_subdriver (non-SHUT mode): matching a device...

   0.958505         [D3] match_function_regex: matching a device...

   0.958605         [D2] Device matches

   0.958636         [D2] Reading first configuration descriptor

   0.958682         [D3] libusb_kernel_driver_active() returned 1 (driver active)

   0.958715         [D2] successfully set kernel driver auto-detach flag

   0.961730         [D2] Claimed interface 0 successfully

   0.961788         [D3] nut_usb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)

  0.962067         [D2] Unable to get HID descriptor (Pipe error)

   0.962127         [D3] HID descriptor length (method 1) -1

   0.962169         [D3] HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22 e1 01

   0.962201         [D3] HID descriptor length (method 2) 481

   0.962309         [D2] HID descriptor length 481

   0.962697         [D2] Unable to get Report descriptor: Resource temporarily unavailable

…

  0.963687          [D2] libusb1: No appropriate HID device found

   0.963784         libusb1: Could not open any HID devices: insufficient permissions on everything

   0.963810         No matching HID UPS found

 

 

Thanks for your help.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230327/c694baad/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ups-trace.txt.gz
Type: application/x-gzip
Size: 4215 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230327/c694baad/attachment-0001.bin>