UPS NUT HID Broken after upgrading to V8.2

crankshaft

New Member
Mar 8, 2023
8
1
3
Upgraded to V8 yesterday, the upgrade went smoothly but have several problems that were introduced with the upgrade most have been fixed / worked around but I am unable to solve the inability for the USB HID driver to work.

I have googled and viewed probably 30 posts reporting similar issues and tried them all but it does not fix the problem.

NUT has been working for 2+ years on version 7 but on version 8 it just refuses to connect.

Here's the output of the nut driver in Debug mode:
Bash:
# /usr/lib/nut/usbhid-ups -a eatonElipse -DD -d1
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
   0.000000    [D1] debug level is '2'
   0.000439    [D2] Initializing an USB-connected UPS with library libusb-1.0.26 (API: 0x1000109) (NUT subdriver name='USB communication driver (libusb 1.0)' ver='0.43')
   0.000446    [D1] upsdrv_initups (non-SHUT)...
   0.002177    [D2] Checking device 1 of 8 (1D6B/0003)
   0.002190    [D1] Failed to open device (1D6B/0003), skipping: Access denied (insufficient permissions)
   0.002191    [D2] Checking device 2 of 8 (10C4/EA60)
   0.002195    [D1] Failed to open device (10C4/EA60), skipping: Access denied (insufficient permissions)
   0.002196    [D2] Checking device 3 of 8 (8087/0026)
   0.002199    [D1] Failed to open device (8087/0026), skipping: Access denied (insufficient permissions)
   0.002200    [D2] Checking device 4 of 8 (0463/FFFF)
   1.002437    [D1] nut_libusb_open get iManufacturer failed, retrying...
   2.002581    [D1] nut_libusb_open get iManufacturer failed, retrying...
   2.190407    [D1] nut_libusb_open get iManufacturer failed, retrying...
   2.776059    [D2] - VendorID: 0463
   2.776072    [D2] - ProductID: ffff
   2.776074    [D2] - Manufacturer: unknown
   2.776076    [D2] - Product: Ellipse ECO
   2.776077    [D2] - Serial Number: 000000000
   2.776079    [D2] - Bus: 003
   2.776080    [D2] - Device: unknown
   2.776081    [D2] - Device release number: 0100
   2.776083    [D2] Trying to match device
   2.776084    [D2] match_function_subdriver (non-SHUT mode): matching a device...
   2.776088    [D2] Device matches
   2.776089    [D2] Reading first configuration descriptor
   2.776106    [D2] Claimed interface 0 successfully
   2.904534    [D2] HID descriptor length 909
   7.904734    [D2] Unable to get Report descriptor: Resource temporarily unavailable
   7.904767    [D2] Checking device 5 of 8 (1D6B/0002)
   7.904786    [D1] Failed to open device (1D6B/0002), skipping: Access denied (insufficient permissions)
   7.904803    [D2] Checking device 6 of 8 (0781/55AE)
   7.904810    [D1] Failed to open device (0781/55AE), skipping: Access denied (insufficient permissions)
   7.904812    [D2] Checking device 7 of 8 (1D6B/0003)
   7.904816    [D1] Failed to open device (1D6B/0003), skipping: Access denied (insufficient permissions)
   7.904819    [D2] Checking device 8 of 8 (1D6B/0002)
   7.904823    [D1] Failed to open device (1D6B/0002), skipping: Access denied (insufficient permissions)
   7.904826    [D2] libusb1: No appropriate HID device found
   7.904830    libusb1: Could not open any HID devices: insufficient permissions on everything
   7.904834    No matching HID UPS found

As you can see it finds the UPS and matches it, but then it ends with:
Code:
libusb1: Could not open any HID devices: insufficient permissions on everything
and that is the string that I have googled and trawled through so many posts none of which resolved the problem.

Changing the config in ups.conf and adding the bus, device, vendorid, productid as suggested by some posts makes no difference and the output is the same. It appears to detect the UPS but has insufficient permission to access it.

The run folder is owned by nut:


Code:
# ls /run/nut -all
total 4
drwxrwx---  3 root nut    80 Jun 18 01:08 .
drwxr-xr-x 31 root root 1480 Jun 18 00:00 ..
drwxrwx---  2 nut  nut    40 Jun 17 12:40 upssched
-rw-r--r--  1 nut  nut     7 Jun 18 01:08 usbhid-ups-eatonElipse.pid


and trying to start the driver:

Code:
# upsdrvctl start
Network UPS Tools - UPS driver controller 2.8.0
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
libusb1: Could not open any HID devices: insufficient permissions on everything
No matching HID UPS found
Driver failed to start (exit status=1)

https://forum.proxmox.com/threads/nut-insufficient-permissions-on-everything.134350/post-593293 - this is not applicable as my config does not include those params, and adding them makes no difference:

enabling the bus, device, vendorid, productid has no effect and the error is the same.

Code:
[eatonElipse]
  driver = usbhid-ups
  port = auto
  desc = "EATON Elipse ECO 650 UPS"
  #bus = 003
  #device = 002
  #vendorid = 0463
  #productid = ffff
  #serial = 000000000
  #offdelay=60   
  #ondelay=70
  # Power down the server at a higher battery charge level (40%) than default 20%
  # This should help with older, weaker batteries
  ignorelb = yes
  override.battery.charge.low = 20

Also created a udev rule and loaded it, made no difference:

Code:
# /etc/udev/rules.d/99-usb_ups.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0463", ATTRS{idProduct}=="ffff", MODE="0666"
SUBSYSTEM=="usb_device", ATTRS{idVendor}=="0463", ATTRS{idProduct}=="ffff", MODE="0666"

## reload rules:
udevadm control --reload-rules

Also tried to change permission on the usb device, no difference:

Code:
lsusb | grep UPS
>> Bus 003 Device 002: ID 0463:ffff MGE UPS Systems UPS
chmod o+w /dev/bus/usb/003/002

This person has same issue but no replies: https://forum.proxmox.com/threads/unable-to-run-nut.146803/

any suggestions / help appreciated as I have exhausted my ideas, Is anybody else using NUT/UPS on proxmox 8 using the usbhid-ups driver successfully ? - is it only me that is facing this problem after upgrading ?[/code]
 
Last edited:
well I don't know why as I have rebooted several times, but I just rebooted and its all back to normal now.

Obviously something I did resolved it, but sadly I can not be sure what it was.

But thanks for helping.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!