<div dir="ltr"><div>>
Can't open /run/nut/nutdrv_qx-ups1: No such file or directory</div><div><br></div><div>That's the driver checking if another instance of it is running. Newer releases should log it less frighteningly.</div><div><br></div><div>> ...
but nut-driver complained so...</div><div><br></div><div>The `nut-driver@upsname` is a systemd instance wrapping an execution of a NUT driver program as a daemon. It is the driver program that actually complains, and its debug logs we want to see to figure out what puzzle pieces did not fit together.</div><div><br></div><div>For an in-vivo debug bump (so the detailed logs end up in systemd journal) you can also temporarily set `debug_min` in the `ups.conf`, see <a href="https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity">https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity</a> for more details (they varied from one NUT release to another).</div><div><br></div><div>Jim</div><div><br></div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, Dec 17, 2025 at 9:45 AM Stephen Davies <<a href="mailto:sdavies@sdc.com.au">sdavies@sdc.com.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks for the feedback.<br>
<br>
The NUT vwersion is 2.8.2.1.<br>
<br>
I am in the process of building a new Rocky Linux 10 server after my old <br>
Centos 7 server died.<br>
<br>
The old box used upsSmart to access the UPS but that relies on an X <br>
server and does not work on ocky 10.<br>
<br>
One of the errors from your suggested test is:<br>
<br>
Can't open /run/nut/nutdrv_qx-ups1: No such file or directory<br>
<br>
I had "langid_fix=0x0409" in ups.conf but nut-driver complained so I <br>
removed it.<br>
<br>
Cheers,<br>
Stephen<br>
<br>
On 17/12/25 18:47, Jim Klimov wrote:<br>
> Cheers,<br>
> <br>
> What NUT version is involved? Per `nut-driver@ups1` I suppose it is <br>
> some v2.8.x, and reports like <a href="https://github.com/networkupstools/nut/" rel="noreferrer" target="_blank">https://github.com/networkupstools/nut/</a> <br>
> pull/638 <<a href="https://github.com/networkupstools/nut/pull/638" rel="noreferrer" target="_blank">https://github.com/networkupstools/nut/pull/638</a>> and https:// <br>
> <a href="http://github.com/networkupstools/nut/issues/674" rel="noreferrer" target="_blank">github.com/networkupstools/nut/issues/674</a> <<a href="https://github.com/" rel="noreferrer" target="_blank">https://github.com/</a> <br>
> networkupstools/nut/issues/674> suggest the needed support was merged <br>
> before v2.8.0, so that should suffice.<br>
> <br>
> It may well be that the manufacturer moved on and stamped the same <br>
> label onto a completely unrelated device (or firmware), these things <br>
> sadly tend to happen as products evolve.<br>
> <br>
> One of those discussions starts with a "|Device not supported|" <br>
> initially, but then it gets found "after opening and then closing the <br>
> OEM software" (UPSmart), and apparently by the end of the ticket they <br>
> got it working right away. The new hunnox subdriver introduced in PR 638 <br>
> changed the initialization to work with that, per <a href="https://github.com/" rel="noreferrer" target="_blank">https://github.com/</a> <br>
> networkupstools/nut/pull/638#issuecomment-443558510 <<a href="https://github.com/" rel="noreferrer" target="_blank">https://github.com/</a> <br>
> networkupstools/nut/pull/638#issuecomment-443558510> - notably there's a <br>
> sleep involved before the device returns valid info; maybe your device <br>
> or its firmware needs a longer one or something?<br>
> <br>
> Compared to settings in those tickets and HCL, your setup misses a <br>
> `langid_fix=0x0409` line, not sure if that makes the difference. This <br>
> seems to be a hardcoded default in hunnox_protocol() initializer at <br>
> <a href="https://github.com/networkupstools/nut/pull/638/changes#diff-" rel="noreferrer" target="_blank">https://github.com/networkupstools/nut/pull/638/changes#diff-</a> <br>
> cb890ac7b82cb7a4f861284bcf39cc4f168312b61cb9455eb2755e345c0aa627R692- <br>
> R696 <<a href="https://github.com/networkupstools/nut/pull/638/changes#diff-" rel="noreferrer" target="_blank">https://github.com/networkupstools/nut/pull/638/changes#diff-</a> <br>
> cb890ac7b82cb7a4f861284bcf39cc4f168312b61cb9455eb2755e345c0aa627R692-R696><br>
> <br>
> Can you start the driver with higher verbosity to collect what/how it <br>
> probes of the device, and how that fails (with what errors), e.g.<br>
> <br>
> |nutdrv_qx -a ups1 -d 1 -DDDDDD|<br>
> <br>
> If there would be a long wall of text, maybe follow up with that as a <br>
> new GitHub issue?<br>
> <br>
> Hope this helps,<br>
> Jim Klimov<br>
> <br>
> <br>
> <br>
> On Wed, Dec 17, 2025 at 8:23 AM Stephen Davies via Nut-upsuser <nut- <br>
> <a href="mailto:upsuser@alioth-lists.debian.net" target="_blank">upsuser@alioth-lists.debian.net</a> <mailto:<a href="mailto:nut-upsuser@alioth-" target="_blank">nut-upsuser@alioth-</a> <br>
> <a href="http://lists.debian.net" rel="noreferrer" target="_blank">lists.debian.net</a>>> wrote:<br>
> <br>
> According to the support list, the Digitech 650VA UPS is supported but<br>
> when I try to connect to my unit, I get:<br>
> nut-driver@ups1[357464]: Device not supported!<br>
> <br>
> My ips.conf has:<br>
> [ups1]<br>
> driver = nutdrv_qx<br>
> port = auto<br>
> vendorid=0001<br>
> productid=0000<br>
> protocol=hunnox<br>
> novendor<br>
> noscanlangid<br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> Nut-upsuser mailing list<br>
> <a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a> <mailto:<a href="mailto:Nut-upsuser@alioth-" target="_blank">Nut-upsuser@alioth-</a><br>
> <a href="http://lists.debian.net" rel="noreferrer" target="_blank">lists.debian.net</a>><br>
> <a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
> <<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a>><br>
> <br>
</blockquote></div>