<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">It doesn’t seem to start the driver for the 1050g2. Device<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"># systemctl restart nut-driver@1050g2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Job for nut-driver@1050g2.service failed because the control process exited with error code.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">See "systemctl status nut-driver@1050g2.service" and "journalctl -xeu nut-driver@1050g2.service" for details.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Journalctl for the driver<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:33:49 cracker systemd[1]: nut-driver@1050g2.service: Scheduled restart job, restart counter is at 1.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:33:49 cracker systemd[1]: Starting nut-driver@1050g2.service - Network UPS Tools - device driver for 1050g2...<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:33:49 cracker nut-driver@1050g2[12320]: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:33:49 cracker nut-driver@1050g2[12350]: Network UPS Tools 2.8.4 release - Generic HID driver 0.67<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:33:49 cracker nut-driver@1050g2[12350]: USB communication driver (libusb 1.0) 0.50<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:33:49 cracker nut-driver@1050g2[12350]: Can't claim USB device [051d:0002]@0/0/0: Other error<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:33:49 cracker nut-driver@1050g2[12350]: upsnotify: notify about state NOTIFY_STATE_STOPPING with libsystemd: was requested, but not running as a service unit now, will not spam more about
it<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:33:49 cracker nut-driver@1050g2[12320]: Driver failed to start (exit status=1)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">And the 850g2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"># systemctl restart nut-driver@850g2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Job for nut-driver@850g2.service failed because the control process exited with error code.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">See "systemctl status nut-driver@850g2.service" and "journalctl -xeu nut-driver@850g2.service" for details<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:34:32 cracker nut-driver@850g2[12874]: Network UPS Tools 2.8.4 release - Generic HID driver 0.67<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:34:32 cracker nut-driver@850g2[12874]: USB communication driver (libusb 1.0) 0.50<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:34:32 cracker nut-driver@850g2[12874]: Can't claim USB device [051d:0002]@0/0/0: Other error<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:34:32 cracker nut-driver@850g2[12874]: upsnotify: notify about state NOTIFY_STATE_STOPPING with libsystemd: was requested, but not running as a service unit now, will not spam more about
it<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:34:32 cracker nut-driver@850g2[12817]: Driver failed to start (exit status=1)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:34:32 cracker systemd[1]: nut-driver@850g2.service: Control process exited, code=exited, status=1/FAILURE<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:34:32 cracker systemd[1]: nut-driver@850g2.service: Failed with result 'exit-code'.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">May 02 17:34:32 cracker systemd[1]: Failed to start nut-driver@850g2.service - Network UPS Tools - device driver for 850g2.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">What does this “other error” mean ? How is this driver attempting to access the device(s) ?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">These device files are accessible by he nut group:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">[root@cracker ~]# ls -lrt /dev/bus/usb/001/00*<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">crw-rw-r-- 1 root root 189, 0 May 2 17:19 /dev/bus/usb/001/001<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">crw-rw---- 1 root nut 189, 2 May 2 17:35 /dev/bus/usb/001/003<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">crw-rw---- 1 root nut 189, 8 May 2 17:35 /dev/bus/usb/001/009<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">[root@cracker ~]#<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Charles Lepple <clepple@gmail.com>
<br>
<b>Sent:</b> 30 April 2026 12:25<br>
<b>To:</b> Gavin Davenport <gavdav@gavdav.net><br>
<b>Cc:</b> Nut-upsuser <nut-upsuser@alioth-lists.debian.net><br>
<b>Subject:</b> Re: [Nut-upsuser] Two APC UPS deivces, Fedora, slightly lost<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I haven't used NUT on Fedora, but your ups.conf seems to be on the right track (symlinks will not help for devices supported by usbhid-ups).<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">There are not many USB product IDs for APC UPSes, but do you get different IDs from "lsusb -d 051d:? Matching product IDs uses simpler logic than matching strings.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A while back, we had issues with Linux guests not getting all of the USB information when on an ESXi hypervisor. That may not be the case if your host machine is physical, but there is still a possibility that the driver is having trouble
during the stage when it iterates through all of the USB devices to retrieve strings like serial numbers. Check the logs for any messages saying that the driver couldn't read the serial number - probably from something like "journalctl -t usbhid-ups". Specifics
of increasing the driver debug level may depend on your version of NUT (and whether/how the packager changed the systemd service definitions).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If that doesn't work, you can try plugging the UPSes into different USB ports (i.e. not into a hub) and using the "bus" parameter in ups.conf, which may need to be adjusted after a major kernel upgrade if the USB stack enumerates the buses
in a different order.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">-- <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Charles Lepple<br>
clepple@gmail<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Apr 29, 2026, at 6:55 PM, Gavin Davenport <<a href="mailto:gavdav@gavdav.net">gavdav@gavdav.net</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">I have 2 APC UpS devices – I have a group of 4 machines connected to various outputs on them and they are connected by USB to the same fedora host.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I’m having issues with nut reliabl discovering both devices<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Here’s my ups.conf<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> [850g2]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> driver = usbhid-ups<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> port = auto<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> desc = "APC Back-UPS ES 850G2"<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> serial = 5B1932T42066<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> [1050g2]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> driver = usbhid-ups<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> port = auto<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> desc = "APC Back-UPS BE1050G2"<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> serial = 9B2545A15277<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I’m hoping nut will match on the serial number of the device.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I’ve been rather led astray by chatgpt making stuff up and then forgetting where it is – so I’m a bit confused about whether I try to have udev prepare the appropriate symlinks for nut<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I’ve had this working (2 Ups devices being monitored, but all a bit hand-cranked). I can’t get it to survive a reboot.<br>
<br>
Are there any known issues with using 2 APC Ups devices which announce themselves very similarly ?<o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif">_______________________________________________<br>
Nut-upsuser mailing list<br>
</span><a href="mailto:Nut-upsuser@alioth-lists.debian.net"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif">Nut-upsuser@alioth-lists.debian.net</span></a><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif"><br>
</span><a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</span></a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>