search for: x2ddriver

...? ? ? ? ? ? ?loaded active running ? Network UPS Tools - power device monitor and shutdown controller ?nut-server.service ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? loaded active running ? Network UPS Tools - power devices information server ?system-nut\x2ddriver.slice ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? loaded active active ? ?Slice /system/nut-driver ?nut-driver.target ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?loaded active active ? ?Network UPS Tools - target for p...

...000:00:14.0-5.2/input0 2023-01-28T09:07:06+1100 kernel: usb 1-5.2: Product: UPS VALUE 2023-01-28T09:07:06+1100 kernel: hid-generic 0003:0764:0501.0008: hiddev96,hidraw2: USB HID v1.10 Device [CPS UPS VALUE] on usb-0000:00:14.0-5.2/input0 2023-01-28T09:07:12+1100 systemd[1]: Created slice system-nut\x2ddriver.slice - Slice /system/nut-driver. 2023-01-28T09:07:12+1100 udevadm[666]: systemd-udev-settle.service is deprecated. Please fix nut-driver at ups.service, multipathd.service not to pull it in. 2023-01-28T09:07:15+1100 systemd[1]: Starting nut-driver at ups.service - Network UPS Tools - device driver...

...-checksum.conf, nut-driver-enumerator-generated.conf Active: active (running) since Fri 2024-11-01 01:26:41 CET; 14h ago Main PID: 1141 (usbhid-ups) Tasks: 1 (limit: 9284) Memory: 1.0M (peak: 1.9M) CPU: 43.317s CGroup: /system.slice/system-nut\x2ddriver.slice/nut-driver at apcupskelder.service ??1141 /lib/nut/usbhid-ups -a apcupskelder nov 01 01:26:40 MinipcLG2 nut-driver at apcupskelder[1068]: HIDParse: LogMax is less than LogMin. Vendor HID report descriptor may be incorrect; interpreting > nov 01 01:26:40 MinipcL...

Look in the startup logs and see where itnis starting. I'm not at a RH system at the moment, but at work, I have had to do this, so can look there,mor perhaps put Nut on the test RH8 VM I spun up for other rrasons on Friday and work out the syntax. Not sure if the systemd file you are using came in the RPM or not, but if it did, it's almost a crime that this critical detail was overlooked.

Hello, I was thinking about what could be going wrong here, and a few ideas pop up: 1) If you installed NUT from packaging, there should have been no need to add OS groups/users manually. There is a valid use-case for running different daemons under different accounts, as long as they talk over network and access same files or UNIX sockets at best by sharing a group for that, but it does need