Arch Linux

Wodger

Member

Registered: 2020-11-30

Posts: 26

NUT and UPS [SOLVED]

Hi All,

I had a problem before with my Eaton 5E UPS constantly disconnecting/reconnecting every 20 seconds and I appear to have solved it using a USB Quirks entry in the boot parameter.

After following through the Wiki guide for NUT, I can reboot, and once in desktop (KDE Plasma), the battery icon is present on the taskbar, and is showing empty and red. If I now run

 sudo upsdrvctl start 

in terminal, the battery icon disappears and NUT takes over.

Looking in the logs it shows UPSDRVCTL during boot trying to attach to the UPS, but it fails, saying it can't find a matching HID.

Not sure how to get this started properly on boot, rather than manually starting it everytime once in desktop. Could it be a different driver is taking control of the device first?

Pete

Last edited by Wodger (2021-08-23 00:21:32)

Wodger

Member

Registered: 2020-11-30

Posts: 26

Re: NUT and UPS [SOLVED]

I was tired when I posted the above, I have included the relevant log from journal to help if possible (-r switch used so its upside down):

Aug 22 08:24:45 wodgersarch systemd[1]: Started Network UPS Tools - power device monitor and shutdown controller.
Aug 22 08:24:45 wodgersarch mtp-probe[1056]: bus: 2, device: 4 was not an MTP device
Aug 22 08:24:45 wodgersarch mtp-probe[1056]: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.2"
Aug 22 08:24:45 wodgersarch systemd[1]: nut-monitor.service: Supervising process 1053 which is not our child. We'll most likely not notice when it exits.
Aug 22 08:24:45 wodgersarch systemd[1]: nut-monitor.service: Can't open PID file /run/nut/upsmon.pid (yet?) after start: Operation not permitted
Aug 22 08:24:45 wodgersarch upsmon[1052]: Startup successful
Aug 22 08:24:45 wodgersarch upsmon[1051]: UPS: Eaton5E@localhost (master) (power value 1)
Aug 22 08:24:45 wodgersarch upsmon[1051]: Using power down flag file /etc/killpower
Aug 22 08:24:45 wodgersarch upsmon[1051]: fopen /run/nut/upsmon.pid: No such file or directory
Aug 22 08:24:45 wodgersarch systemd[1]: Starting Network UPS Tools - power device monitor and shutdown controller...
Aug 22 08:24:45 wodgersarch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nut-server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 22 08:24:45 wodgersarch systemd[1]: Started Network UPS Tools - power devices information server.
Aug 22 08:24:45 wodgersarch upsd[1049]: Startup successful
Aug 22 08:24:45 wodgersarch upsd[1047]: Can't connect to UPS [Eaton5E] (usbhid-ups-Eaton5E): Connection refused
Aug 22 08:24:45 wodgersarch upsd[1047]: Can't connect to UPS [Eaton5E] (usbhid-ups-Eaton5E): Connection refused
Aug 22 08:24:45 wodgersarch upsd[1047]: listening on ::1 port 3493
Aug 22 08:24:45 wodgersarch upsd[1047]: listening on ::1 port 3493
Aug 22 08:24:45 wodgersarch upsd[1047]: listening on 127.0.0.1 port 3493
Aug 22 08:24:45 wodgersarch upsd[1047]: listening on 127.0.0.1 port 3493
Aug 22 08:24:45 wodgersarch upsd[1047]: fopen /run/nut/upsd.pid: No such file or directory
Aug 22 08:24:45 wodgersarch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ipp-usb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 22 08:24:45 wodgersarch systemd[1]: ipp-usb.service: Deactivated successfully.
Aug 22 08:24:45 wodgersarch mtp-probe[1045]: bus: 2, device: 4 was not an MTP device
Aug 22 08:24:45 wodgersarch mtp-probe[1045]: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.2"
Aug 22 08:24:45 wodgersarch systemd[1]: Starting Network UPS Tools - power devices information server...
Aug 22 08:24:45 wodgersarch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nut-driver comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Aug 22 08:24:45 wodgersarch systemd[1]: Failed to start Network UPS Tools - power device driver controller.
Aug 22 08:24:45 wodgersarch systemd[1]: nut-driver.service: Failed with result 'exit-code'.
Aug 22 08:24:45 wodgersarch systemd[1]: nut-driver.service: Control process exited, code=exited, status=1/FAILURE
Aug 22 08:24:45 wodgersarch upsdrvctl[475]: Network UPS Tools - UPS driver controller 2.7.4
Aug 22 08:24:45 wodgersarch upsdrvctl[475]: Driver failed to start (exit status=1)
Aug 22 08:24:45 wodgersarch upsdrvctl[479]: No matching HID UPS found
Aug 22 08:24:45 wodgersarch upsdrvctl[479]: USB communication driver 0.33
Aug 22 08:24:45 wodgersarch upsdrvctl[479]: Network UPS Tools - Generic HID driver 0.41 (2.7.4)
Aug 22 08:24:45 wodgersarch kernel: hid-generic 0003:0463:FFFF.000A: hiddev97,hidraw9: USB HID v1.10 Device [EATON 5E] on usb-0000:00:14.0-1.2/input0

Pete

Wodger

Member

Registered: 2020-11-30

Posts: 26

Re: NUT and UPS [SOLVED]

Hi All,

I had a problem before with my Eaton 5E UPS constantly disconnecting/reconnecting every 20 seconds and I appear to have solved it using a USB Quirks entry in the boot parameter.

After following through the Wiki guide for NUT, I can reboot, and once in desktop (KDE Plasma), the battery icon is present on the taskbar, and is showing empty and red. If I now run

 sudo upsdrvctl start 

in terminal, the battery icon disappears and NUT takes over.

Looking in the logs it shows UPSDRVCTL during boot trying to attach to the UPS, but it fails, saying it can't find a matching HID.

Not sure how to get this started properly on boot, rather than manually starting it everytime once in desktop. Could it be a different driver is taking control of the device first?

Pete

So after some more investigation, I installed nut onto one of my other distro systems (Kubuntu), and was surprised that in the UPS.conf file, there was an additional command by default: "maxretry = 3". More investigation proved this was the missing link, and after adding this into my arch system, the UPS connects no problem on boot - happy camper

Pete