Talk:Network UPS Tools

From ArchWiki

Can't claim USB device error

Excellent guide, the comment on permission and requiring /etc/udev/rules.d/50-ups.rules was exactly the problem installing the latest version from AUR. I would vote for Arch packaging NUT again as it is essential for all but APC compatibles UPSs that use apcupsd. David C. Rankin, J.D.,P.E. -- Rankin Law Firm, PLLC (talk) 04:34, 13 May 2019 (UTC)

Change in systemd units after update to NUT 2.8.0

This might just be an issue with my config, but it appears that after updating to 2.8.0 nut-server.service can no longer start the appropriate nut-driver by itself:

  • nut-driver.service is gone, and one must instead manually run nut-driver-enumerator.service which creates the needed nut-driver@<ups_name>.service link (wanted by the new
  • There's also nut-driver-enumerator.path which monitors /etc/nut/ups.conf and runs the service when it's changed.
  • Finally, there's a new which pulls the server and monitor services as well as the new driver target.

--FeralHedgehog (talk) 18:19, 2 May 2022 (UTC)

Needs revision

I have just installed 2.8.0 and the guidance given is no longer correct. The comment above by FeralHedgehog helped me to get it going but someone with good knowledge of systemd & NUT needs to redo the wiki page with some explanation as to what the various .service & .target files do . If I get time I might give it a go, but don't count on it! Vario (talk) 08:57, 9 June 2022 (UTC)

Starting on boot

I had trouble getting NUT (v2.8.0) to start on boot when enabling the units in this guide. Starting those units manually one by one did work. I disabled all of them and enabled just and nothing else, and that seems start NUT correctly when rebooting. I guess that's the way it's supposed to work now in 2.8.0(?).

--Zebibit (talk) 17:51, 5 September 2022