Hi Jim Thanks for the info. Nut runs on bare metal, there is no virtualization layer. I will have a look at the github post after writing this post. I have compiled and installed nut 2.8.2 as suggested. But now I am confused: Where is the usb-hid driver, which I used in Nut 2.8.0? Does one need to pass a special flag to configure to build it?
Yours Stefan Am Fr., 5. Juli 2024 um 18:52 Uhr schrieb Jim Klimov <[email protected]>: > > Did you check also that `upsc` client does not report anything about the > device? > > The message indicates that some other process has a hold on the USB devfs > node, and those can typically be either other copies of a NUT driver, rarely > some other programs that see and grab HID devices, or in case of > virtualization and pass-through - the device being busy in the guest or host > system (other than the one NUT runs in, so harder to debug or notice specific > symptoms). > > With NUT v2.8.0 and newer on a Linux (or illumos) system I'd guess the > `nut-driver-enumerator` service integration has spawned a `nut-driver@Eaton` > instance and that is what is holding the device. A systemd unit may have been > started without a PID file, so the copy started from command line does not > see that one to kill off (as NUT drivers usually do since the dawn of time, > assuming a frozen older copy). > > More details here: > https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE) > > Newer NUT versions should be more informative in the log about such > situations, as well as capable of communicating with the older copy (if it is > not frozen) over Unix sockets "intelligently" instead of sending bare-bone > signals to reload or exit with no feedback. > > Jim > > > > > On Fri, Jul 5, 2024 at 1:16 PM Stefan Schumacher via Nut-upsuser > <[email protected]> wrote: >> >> Hello >> >> Initial Disclaimer: I used this tutorial. I know its in german but the >> entries to be made in the configuration files are marked and should be >> able to identify if there are any errors. >> >> https://techbotch.org/blog/ups-setup/index.html >> >> After several power failures and damaged fuses I decided to give Eaton >> & Nut another try. Eaton because the model I bought seems to be the >> one on the market which has the most power without a permanent fan. >> Unfortunately I don't even get as far as the last time. Lets begin >> with the basic info: >> >> I am using: Debian Bookworm 12.6 with these packages, which were >> installed from the official Debian Repository. >> ii nut 2.8.0-7 >> all network UPS tools - metapackage >> ii nut-client 2.8.0-7 >> amd64 network UPS tools - clients >> ii nut-server 2.8.0-7 >> amd64 network UPS tools - core system >> >> My device is a: https://www.eaton.com/de/de-de/skuPage.EL1600USBDIN.html >> >> There is a connection between the USV and the server it protects. >> lsusb = Bus 001 Device 002: ID 0463:ffff MGE UPS Systems UPS >> >> What follows is the output of the driver. As you can see I am running >> it as root. What are the next steps I should take? >> >> Thanks in advance >> Stefan Malte >> >> root@mars:/usr/lib/nut# ./usbhid-ups -DD -a Eaton >> 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.001566 [D2] Initializing an USB-connected UPS with library >> libusb-1.0.26 (API: 0x1000109) (NUT subdriver name='USB communication >> driver (libusb 1.0)' > >> 0.001575 [D1] upsdrv_initups (non-SHUT)... >> 0.004892 [D2] Checking device 1 of 7 (1D6B/0003) >> 0.004908 [D1] Failed to open device (1D6B/0003), skipping: >> Access denied (insufficient permissions) >> 0.004911 [D2] Checking device 2 of 7 (0BDA/5452) >> 0.004917 [D1] Failed to open device (0BDA/5452), skipping: >> Access denied (insufficient permissions) >> 0.004921 [D2] Checking device 3 of 7 (1D6B/0002) >> 0.004926 [D1] Failed to open device (1D6B/0002), skipping: >> Access denied (insufficient permissions) >> 0.004929 [D2] Checking device 4 of 7 (1D6B/0003) >> 0.004937 [D1] Failed to open device (1D6B/0003), skipping: >> Access denied (insufficient permissions) >> 0.004941 [D2] Checking device 5 of 7 (0463/FFFF) >> 0.463157 [D2] - VendorID: 0463 >> 0.463198 [D2] - ProductID: ffff >> 0.463215 [D2] - Manufacturer: EATON >> 0.463231 [D2] - Product: Ellipse ECO >> 0.463249 [D2] - Serial Number: 000000000 >> 0.463268 [D2] - Bus: 001 >> 0.463287 [D2] - Device: unknown >> 0.463314 [D2] - Device release number: 0100 >> 0.463332 [D2] Trying to match device >> 0.463350 [D2] match_function_subdriver (non-SHUT mode): >> matching a device... >> 0.463603 [D2] Device matches >> 0.463624 [D2] Reading first configuration descriptor >> 0.463662 [D2] failed to claim USB device: Resource busy >> 0.463689 [D2] Kernel driver already detached >> 0.463714 [D2] failed to claim USB device: Resource busy >> 0.463740 [D2] Kernel driver already detached >> 0.463764 [D2] failed to claim USB device: Resource busy >> 0.463787 [D2] Kernel driver already detached >> 0.463809 [D2] failed to claim USB device: Resource busy >> 0.463831 [D2] Kernel driver already detached >> 0.463854 Can't claim USB device [0463:ffff]@0/0: Entity not found >> >> _______________________________________________ >> Nut-upsuser mailing list >> [email protected] >> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
