thr3ads.net - Nut upsuser - [Nut-upsuser] Digitech support [Dec 2025]

If this information is useful, please help other people find it:
Share via:

Jim Klimov

2025-Dec-17 10:03 UTC

[Nut-upsuser] Digitech support

>  Can't open /run/nut/nutdrv_qx-ups1: No such file or directory
That's the driver checking if another instance of it is running. Newer
releases should log it less frighteningly.
> ... but nut-driver complained so...
The `nut-driver at 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.

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
https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug-verbosity
for
more details (they varied from one NUT release to another).

Jim



On Wed, Dec 17, 2025 at 9:45?AM Stephen Davies <sdavies at sdc.com.au>
wrote:
> Thanks for the feedback.
>
> The NUT vwersion is 2.8.2.1.
>
> I am in the process of building a new Rocky Linux 10 server after my old
> Centos 7 server died.
>
> The old box used upsSmart to access the UPS but that relies on an X
> server and does not work on ocky 10.
>
> One of the errors from your suggested test is:
>
> Can't open /run/nut/nutdrv_qx-ups1: No such file or directory
>
> I had "langid_fix=0x0409" in ups.conf but nut-driver complained
so I
> removed it.
>
> Cheers,
> Stephen
>
> On 17/12/25 18:47, Jim Klimov wrote:
> > Cheers,
> >
> >    What NUT version is involved? Per `nut-driver at ups1` I suppose it
is
> > some v2.8.x, and reports like https://github.com/networkupstools/nut/
> > pull/638 <https://github.com/networkupstools/nut/pull/638> and
https://
> > github.com/networkupstools/nut/issues/674 <https://github.com/
> > networkupstools/nut/issues/674> suggest the needed support was
merged
> > before v2.8.0, so that should suffice.
> >
> >    It may well be that the manufacturer moved on and stamped the same
> > label onto a completely unrelated device (or firmware), these things
> > sadly tend to happen as products evolve.
> >
> >    One of those discussions starts with a "|Device not
supported|"
> > initially, but then it gets found "after opening and then closing
the
> > OEM software" (UPSmart), and apparently by the end of the ticket
they
> > got it working right away. The new hunnox subdriver introduced in PR
638
> > changed the initialization to work with that, per https://github.com/
> > networkupstools/nut/pull/638#issuecomment-443558510
<https://github.com/
> > networkupstools/nut/pull/638#issuecomment-443558510> - notably
there's a
> > sleep involved before the device returns valid info; maybe your device
> > or its firmware needs a longer one or something?
> >
> >    Compared to settings in those tickets and HCL, your setup misses a
> > `langid_fix=0x0409` line, not sure if that makes the difference. This
> > seems to be a hardcoded default in hunnox_protocol() initializer at
> > https://github.com/networkupstools/nut/pull/638/changes#diff-
> > cb890ac7b82cb7a4f861284bcf39cc4f168312b61cb9455eb2755e345c0aa627R692-
> > R696 <https://github.com/networkupstools/nut/pull/638/changes#diff-
> >
>
cb890ac7b82cb7a4f861284bcf39cc4f168312b61cb9455eb2755e345c0aa627R692-R696>
> >
> >    Can you start the driver with higher verbosity to collect what/how
it
> > probes of the device, and how that fails (with what errors), e.g.
> >
> > |nutdrv_qx -a ups1 -d 1 -DDDDDD|
> >
> >    If there would be a long wall of text, maybe follow up with that as
a
> > new GitHub issue?
> >
> > Hope this helps,
> > Jim Klimov
> >
> >
> >
> > On Wed, Dec 17, 2025 at 8:23?AM Stephen Davies via Nut-upsuser
<nut-
> > upsuser at alioth-lists.debian.net <mailto:nut-upsuser at alioth-
> > lists.debian.net>> wrote:
> >
> >     According to the support list, the Digitech 650VA UPS is supported
> but
> >     when I try to connect to my unit, I get:
> >     nut-driver at ups1[357464]: Device not supported!
> >
> >     My ips.conf has:
> >     [ups1]
> >     driver = nutdrv_qx
> >     port = auto
> >     vendorid=0001
> >     productid=0000
> >     protocol=hunnox
> >     novendor
> >     noscanlangid
> >
> >
> >
> >     _______________________________________________
> >     Nut-upsuser mailing list
> >     Nut-upsuser at alioth-lists.debian.net <mailto:Nut-upsuser at
alioth-
> >     lists.debian.net>
> >    
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
> >     <
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser>
> >
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20251217/cf8451e7/attachment-0001.htm>

Stephen Davies

2025-Dec-19 07:41 UTC

head link

[Nut-upsuser] Digitech support

I set debug_min to 6 as suggested in your referenced doco.

The resulting log is attached.

Cheers and thanks,
Stephen

On 17/12/25 20:33, Jim Klimov wrote:>  > Can't open /run/nut/nutdrv_qx-ups1: No such file or directory
> 
> That's the driver checking if another instance of it is running. Newer 
> releases should log it less frighteningly.
> 
>  > ... but nut-driver complained so...
> 
> The `nut-driver at 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.
> 
> 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 
> https://github.com/networkupstools/nut/wiki/Changing-NUT-daemon-debug- 
> verbosity <https://github.com/networkupstools/nut/wiki/Changing-NUT- 
> daemon-debug-verbosity>?for more details (they varied from one NUT 
> release to another).
> 
> Jim
> 
> 
> 
> On Wed, Dec 17, 2025 at 9:45?AM Stephen Davies <sdavies at sdc.com.au 
> <mailto:sdavies at sdc.com.au>> wrote:
> 
>     Thanks for the feedback.
> 
>     The NUT vwersion is 2.8.2.1.
> 
>     I am in the process of building a new Rocky Linux 10 server after my
>     old
>     Centos 7 server died.
> 
>     The old box used upsSmart to access the UPS but that relies on an X
>     server and does not work on ocky 10.
> 
>     One of the errors from your suggested test is:
> 
>     Can't open /run/nut/nutdrv_qx-ups1: No such file or directory
> 
>     I had "langid_fix=0x0409" in ups.conf but nut-driver
complained so I
>     removed it.
> 
>     Cheers,
>     Stephen
> 
>     On 17/12/25 18:47, Jim Klimov wrote:
>      > Cheers,
>      >
>      >? ? What NUT version is involved? Per `nut-driver at ups1` I
suppose
>     it is
>      > some v2.8.x, and reports like https://github.com/networkupstools/
>     nut/ <https://github.com/networkupstools/nut/>
>      > pull/638 <https://github.com/networkupstools/nut/pull/638
>     <https://github.com/networkupstools/nut/pull/638>> and
https://
>      > github.com/networkupstools/nut/issues/674 <http://github.com/
>     networkupstools/nut/issues/674> <https://github.com/ <https://
>     github.com/>
>      > networkupstools/nut/issues/674> suggest the needed support was
>     merged
>      > before v2.8.0, so that should suffice.
>      >
>      >? ? It may well be that the manufacturer moved on and stamped the
>     same
>      > label onto a completely unrelated device (or firmware), these
things
>      > sadly tend to happen as products evolve.
>      >
>      >? ? One of those discussions starts with a "|Device not
supported|"
>      > initially, but then it gets found "after opening and then
closing
>     the
>      > OEM software" (UPSmart), and apparently by the end of the
ticket
>     they
>      > got it working right away. The new hunnox subdriver introduced in
>     PR 638
>      > changed the initialization to work with that, per https://
>     github.com/ <https://github.com/>
>      > networkupstools/nut/pull/638#issuecomment-443558510 <https://
>     github.com/ <https://github.com/>
>      > networkupstools/nut/pull/638#issuecomment-443558510>?- notably
>     there's a
>      > sleep involved before the device returns valid info; maybe your
>     device
>      > or its firmware needs a longer one or something?
>      >
>      >? ? Compared to settings in those tickets and HCL, your setup
>     misses a
>      > `langid_fix=0x0409` line, not sure if that makes the difference.
>     This
>      > seems to be a hardcoded default in?hunnox_protocol() initializer
at
>      > https://github.com/networkupstools/nut/pull/638/changes#diff-
>     <https://github.com/networkupstools/nut/pull/638/changes#diff->
>      >
>     cb890ac7b82cb7a4f861284bcf39cc4f168312b61cb9455eb2755e345c0aa627R692-
>      > R696 <https://github.com/networkupstools/nut/pull/638/
>     changes#diff- <https://github.com/networkupstools/nut/pull/638/
>     changes#diff->
>      >
>    
cb890ac7b82cb7a4f861284bcf39cc4f168312b61cb9455eb2755e345c0aa627R692-R696>
>      >
>      >? ? Can you start the driver with higher verbosity to collect
>     what/how it
>      > probes of the device, and how that fails (with what errors), e.g.
>      >
>      > |nutdrv_qx -a ups1 -d 1 -DDDDDD|
>      >
>      >? ? If there would be a long wall of text, maybe follow up with
>     that as a
>      > new GitHub issue?
>      >
>      > Hope this helps,
>      > Jim Klimov
>      >
>      >
>      >
>      > On Wed, Dec 17, 2025 at 8:23?AM Stephen Davies via Nut-upsuser
<nut-
>      > upsuser at alioth-lists.debian.net <mailto:upsuser at alioth-
>     lists.debian.net> <mailto:nut-upsuser at alioth- <mailto:nut-
>     upsuser at alioth->
>      > lists.debian.net <http://lists.debian.net>>> wrote:
>      >
>      >? ? ?According to the support list, the Digitech 650VA UPS is
>     supported but
>      >? ? ?when I try to connect to my unit, I get:
>      >? ? ?nut-driver at ups1[357464]: Device not supported!
>      >
>      >? ? ?My ips.conf has:
>      >? ? ?[ups1]
>      >? ? ?driver = nutdrv_qx
>      >? ? ?port = auto
>      >? ? ?vendorid=0001
>      >? ? ?productid=0000
>      >? ? ?protocol=hunnox
>      >? ? ?novendor
>      >? ? ?noscanlangid
>      >
>      >
>      >
>      >? ? ?_______________________________________________
>      >? ? ?Nut-upsuser mailing list
>      > Nut-upsuser at alioth-lists.debian.net <mailto:Nut-upsuser at
alioth-
>     lists.debian.net> <mailto:Nut-upsuser at alioth- <mailto:Nut-
>     upsuser at alioth->
>      > lists.debian.net <http://lists.debian.net>>
>      > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-
>     upsuser <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
>     nut-upsuser>
>      >? ? ?<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
>     nut-upsuser <https://alioth-lists.debian.net/cgi-bin/mailman/
>     listinfo/nut-upsuser>>
>      >
> -------------- next part --------------
Dec 19 18:04:00 mustang systemd[1]: Stopped nut-driver at ups1.service - Network
UPS Tools - device driver for ups1.
Dec 19 18:04:02 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:07 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:12 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:17 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:22 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:27 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:32 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:37 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:40 mustang systemd[1]: Starting nut-driver at ups1.service -
Network UPS Tools - device driver for ups1...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]: Network UPS Tools - UPS
driver controller 2.8.2.1
Dec 19 18:04:41 mustang nut-driver at ups1[916125]: Network UPS Tools - Generic
Q* USB/Serial driver 0.36 (2.8.2.1)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]: USB communication driver
(libusb 1.0) 0.48
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.000000#011[D1] debug
level is '6'
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.000013#011[D5]
send_to_all: SETINFO driver.debug "6"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.000019#011[D5]
send_to_all: SETFLAGS driver.debug RW NUMBER
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.001028#011[D1] Succeeded
to become_user(nut): now UID=57 GID=57
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.001051#011[D1]
Signalling UPS [ups1]: driver.exit (quietly, no fuss if no driver is running or
responding)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.001065#011Can't open
/run/nut/nutdrv_qx-ups1: No such file or directory
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.001076#011[D1] Request
for other driver to exit returned code -1
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.001082#011[D1] Socket
dialog with the other driver instance (may be absent) failed: No such file or
directory
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.001091#011[D1] PID file
/run/nut/nutdrv_qx-ups1.pid not found; stat() returned -1 (errno=2): No such
file or directory
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.001124#011[D1] Saving
PID 916125 into /run/nut/nutdrv_qx-ups1.pid
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.001152#011[D5]
send_to_all: SETINFO device.type "ups"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.001158#011[D5]
send_to_all: SETINFO driver.state "init.device"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.001162#011[D1]
upsdrv_initups...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.005240#011[D2] Checking
device 1 of 8 (1D6B/0003)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.005264#011[D1] Failed to
open device (1D6B/0003), skipping: Access denied (insufficient permissions)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.005267#011[D2] Checking
device 2 of 8 (17EF/6190)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.005273#011[D1] Failed to
open device (17EF/6190), skipping: Access denied (insufficient permissions)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.005276#011[D2] Checking
device 3 of 8 (17EF/608D)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.005282#011[D1] Failed to
open device (17EF/608D), skipping: Access denied (insufficient permissions)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.005285#011[D2] Checking
device 4 of 8 (0001/0000)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.006554#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.007734#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008949#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008961#011[D2] -
VendorID: 0001
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008963#011[D2] -
ProductID: 0000
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008966#011[D2] -
Manufacturer: unknown
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008968#011[D2] -
Product: unknown
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008971#011[D2] - Serial
Number: unknown
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008974#011[D2] - Bus:
003
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008977#011[D2] - Bus
Port: 006
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008980#011[D2] - Device:
006
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008984#011[D2] - Device
release number: 0100
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008987#011[D2] Trying to
match device
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.008990#011[D3]
match_function_regex: matching a device...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009022#011[D2] Device
matches
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009025#011[D2] Reading
configuration descriptor 1 of 1
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009033#011[D3]
libusb_kernel_driver_active() returned 0: Success
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009053#011[D2] Claimed
interface 0 successfully
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009058#011[D3]
nut_usb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009065#011[D5]
send_to_all: SETINFO ups.vendorid "0001"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009069#011[D5]
send_to_all: SETINFO ups.productid "0000"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009073#011[D2] Skipping
protocol Voltronic 0.08
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009076#011[D2] Skipping
protocol Voltronic-QS 0.09
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009078#011[D2] Skipping
protocol Voltronic-QS-Hex 0.10
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009080#011[D2] Skipping
protocol Mustek 0.08
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009082#011[D2] Skipping
protocol Megatec/old 0.08
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009085#011[D2] Skipping
protocol BestUPS 0.07
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009087#011[D2] Skipping
protocol Mecer 0.08
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009089#011[D2] Skipping
protocol Megatec 0.07
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009091#011[D2] Skipping
protocol Zinto 0.07
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009093#011[D2] Skipping
protocol Masterguard 0.02
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.009104#011[D3] send: Q1
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.010386#011[D3] read:
Input/Output Error (-1)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.010400#011[D5]
send_to_all: SETINFO driver.state "reconnect.trying"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.010528#011[D4]
qx_process: failed to preprocess answer [input.voltage]
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.014823#011[D2] Checking
device 1 of 8 (1D6B/0003)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.014838#011[D1] Failed to
open device (1D6B/0003), skipping: Access denied (insufficient permissions)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.014843#011[D2] Checking
device 2 of 8 (17EF/6190)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.014849#011[D1] Failed to
open device (17EF/6190), skipping: Access denied (insufficient permissions)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.014854#011[D2] Checking
device 3 of 8 (17EF/608D)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.014860#011[D1] Failed to
open device (17EF/608D), skipping: Access denied (insufficient permissions)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.014863#011[D2] Checking
device 4 of 8 (0001/0000)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.016056#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.017244#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018443#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018459#011[D2] -
VendorID: 0001
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018462#011[D2] -
ProductID: 0000
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018465#011[D2] -
Manufacturer: unknown
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018468#011[D2] -
Product: unknown
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018471#011[D2] - Serial
Number: unknown
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018474#011[D2] - Bus:
003
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018476#011[D2] - Bus
Port: 006
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018479#011[D2] - Device:
006
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018482#011[D2] - Device
release number: 0100
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018485#011[D2] Trying to
match device
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018488#011[D3]
match_function_exact: matching a device...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018490#011[D3]
match_function_regex: matching a device...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018499#011[D2] Device
matches
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018502#011[D2] Reading
configuration descriptor 1 of 1
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018510#011[D3]
libusb_kernel_driver_active() returned 0: Success
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018527#011[D2] Claimed
interface 0 successfully
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018531#011[D3]
nut_usb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018539#011[D5]
send_to_all: SETINFO driver.state "reconnect.updateinfo"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.018543#011[D3] send: Q1
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.019696#011[D3] read:
Input/Output Error (-1)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.019703#011[D5]
send_to_all: SETINFO driver.state "reconnect.trying"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.019770#011[D4]
qx_process: failed to preprocess answer [input.voltage]
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.024692#011[D2] Checking
device 1 of 8 (1D6B/0003)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.024708#011[D1] Failed to
open device (1D6B/0003), skipping: Access denied (insufficient permissions)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.024713#011[D2] Checking
device 2 of 8 (17EF/6190)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.024721#011[D1] Failed to
open device (17EF/6190), skipping: Access denied (insufficient permissions)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.024724#011[D2] Checking
device 3 of 8 (17EF/608D)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.024729#011[D1] Failed to
open device (17EF/608D), skipping: Access denied (insufficient permissions)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.024733#011[D2] Checking
device 4 of 8 (0001/0000)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.025964#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.027138#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028359#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028372#011[D2] -
VendorID: 0001
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028379#011[D2] -
ProductID: 0000
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028381#011[D2] -
Manufacturer: unknown
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028384#011[D2] -
Product: unknown
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028387#011[D2] - Serial
Number: unknown
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028390#011[D2] - Bus:
003
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028393#011[D2] - Bus
Port: 006
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028396#011[D2] - Device:
006
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028400#011[D2] - Device
release number: 0100
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028403#011[D2] Trying to
match device
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028406#011[D3]
match_function_exact: matching a device...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028410#011[D3]
match_function_regex: matching a device...
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028416#011[D2] Device
matches
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028419#011[D2] Reading
configuration descriptor 1 of 1
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028424#011[D3]
libusb_kernel_driver_active() returned 0: Success
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028435#011[D2] Claimed
interface 0 successfully
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028439#011[D3]
nut_usb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028445#011[D5]
send_to_all: SETINFO driver.state "reconnect.updateinfo"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.028448#011[D3] send: Q1
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.029620#011[D3] read:
Input/Output Error (-1)
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.029625#011[D5]
send_to_all: SETINFO driver.state "reconnect.trying"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.029690#011[D4]
qx_process: failed to preprocess answer [input.voltage]
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.029696#011[D2] Skipping
protocol Ablerex 0.01
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.029700#011[D2] Skipping
protocol Q1 0.08
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.029703#011Device not
supported!
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.029706#011Device not
supported!
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.029711#011[D5]
send_to_all: SETINFO driver.state "cleanup.exit"
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.029716#011[D6]
upsnotify: notify about state 4 with libsystemd: use sd_notify()
Dec 19 18:04:41 mustang nut-driver at ups1[916125]:   0.029720#011[D6]
upsnotify: posting sd_notify: STATUS=exit_cleanup()
Dec 19 18:04:41 mustang nut-driver at ups1[916125]: STOPPING=1
Dec 19 18:04:41 mustang systemd[1]: nut-driver at ups1.service: Main process
exited, code=exited, status=1/FAILURE
Dec 19 18:04:41 mustang systemd[1]: nut-driver at ups1.service: Failed with
result 'exit-code'.
Dec 19 18:04:41 mustang systemd[1]: Failed to start nut-driver at ups1.service -
Network UPS Tools - device driver for ups1.
Dec 19 18:04:41 mustang nut-server[342574]: Can't connect to UPS [ups1]
(nutdrv_qx-ups1): No such file or directory
Dec 19 18:04:41 mustang upsd[342574]: Can't connect to UPS [ups1]
(nutdrv_qx-ups1): No such file or directory
Dec 19 18:04:42 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:47 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:52 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected
Dec 19 18:04:56 mustang systemd[1]: nut-driver at ups1.service: Scheduled
restart job, restart counter is at 1.
Dec 19 18:04:56 mustang systemd[1]: Starting nut-driver at ups1.service -
Network UPS Tools - device driver for ups1...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]: Network UPS Tools - UPS
driver controller 2.8.2.1
Dec 19 18:04:56 mustang nut-driver at ups1[916173]: Network UPS Tools - Generic
Q* USB/Serial driver 0.36 (2.8.2.1)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]: USB communication driver
(libusb 1.0) 0.48
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000000#011[D1] debug
level is '6'
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000016#011[D5]
send_to_all: SETINFO driver.debug "6"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000023#011[D5]
send_to_all: SETFLAGS driver.debug RW NUMBER
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000821#011[D1] Succeeded
to become_user(nut): now UID=57 GID=57
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000836#011[D1]
Signalling UPS [ups1]: driver.exit (quietly, no fuss if no driver is running or
responding)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000846#011Can't open
/run/nut/nutdrv_qx-ups1: No such file or directory
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000851#011[D1] Request
for other driver to exit returned code -1
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000854#011[D1] Socket
dialog with the other driver instance (may be absent) failed: No such file or
directory
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000860#011[D1] PID file
/run/nut/nutdrv_qx-ups1.pid not found; stat() returned -1 (errno=2): No such
file or directory
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000883#011[D1] Saving
PID 916173 into /run/nut/nutdrv_qx-ups1.pid
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000902#011[D5]
send_to_all: SETINFO device.type "ups"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000905#011[D5]
send_to_all: SETINFO driver.state "init.device"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.000907#011[D1]
upsdrv_initups...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.004841#011[D2] Checking
device 1 of 8 (1D6B/0003)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.004858#011[D1] Failed to
open device (1D6B/0003), skipping: Access denied (insufficient permissions)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.004863#011[D2] Checking
device 2 of 8 (17EF/6190)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.004869#011[D1] Failed to
open device (17EF/6190), skipping: Access denied (insufficient permissions)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.004872#011[D2] Checking
device 3 of 8 (17EF/608D)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.004877#011[D1] Failed to
open device (17EF/608D), skipping: Access denied (insufficient permissions)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.004879#011[D2] Checking
device 4 of 8 (0001/0000)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.006092#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.007280#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008480#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008493#011[D2] -
VendorID: 0001
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008498#011[D2] -
ProductID: 0000
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008500#011[D2] -
Manufacturer: unknown
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008503#011[D2] -
Product: unknown
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008506#011[D2] - Serial
Number: unknown
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008510#011[D2] - Bus:
003
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008513#011[D2] - Bus
Port: 006
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008516#011[D2] - Device:
006
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008520#011[D2] - Device
release number: 0100
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008523#011[D2] Trying to
match device
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008527#011[D3]
match_function_regex: matching a device...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008557#011[D2] Device
matches
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008561#011[D2] Reading
configuration descriptor 1 of 1
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008568#011[D3]
libusb_kernel_driver_active() returned 0: Success
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008590#011[D2] Claimed
interface 0 successfully
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008594#011[D3]
nut_usb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008601#011[D5]
send_to_all: SETINFO ups.vendorid "0001"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008605#011[D5]
send_to_all: SETINFO ups.productid "0000"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008609#011[D2] Skipping
protocol Voltronic 0.08
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008611#011[D2] Skipping
protocol Voltronic-QS 0.09
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008614#011[D2] Skipping
protocol Voltronic-QS-Hex 0.10
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008616#011[D2] Skipping
protocol Mustek 0.08
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008619#011[D2] Skipping
protocol Megatec/old 0.08
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008621#011[D2] Skipping
protocol BestUPS 0.07
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008624#011[D2] Skipping
protocol Mecer 0.08
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008626#011[D2] Skipping
protocol Megatec 0.07
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008628#011[D2] Skipping
protocol Zinto 0.07
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008631#011[D2] Skipping
protocol Masterguard 0.02
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.008635#011[D3] send: Q1
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.009876#011[D3] read:
Input/Output Error (-1)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.009883#011[D5]
send_to_all: SETINFO driver.state "reconnect.trying"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.009978#011[D4]
qx_process: failed to preprocess answer [input.voltage]
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.014604#011[D2] Checking
device 1 of 8 (1D6B/0003)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.014619#011[D1] Failed to
open device (1D6B/0003), skipping: Access denied (insufficient permissions)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.014625#011[D2] Checking
device 2 of 8 (17EF/6190)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.014631#011[D1] Failed to
open device (17EF/6190), skipping: Access denied (insufficient permissions)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.014635#011[D2] Checking
device 3 of 8 (17EF/608D)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.014640#011[D1] Failed to
open device (17EF/608D), skipping: Access denied (insufficient permissions)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.014644#011[D2] Checking
device 4 of 8 (0001/0000)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.015872#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.017030#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018204#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018217#011[D2] -
VendorID: 0001
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018223#011[D2] -
ProductID: 0000
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018226#011[D2] -
Manufacturer: unknown
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018229#011[D2] -
Product: unknown
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018233#011[D2] - Serial
Number: unknown
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018236#011[D2] - Bus:
003
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018239#011[D2] - Bus
Port: 006
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018242#011[D2] - Device:
006
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018246#011[D2] - Device
release number: 0100
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018249#011[D2] Trying to
match device
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018252#011[D3]
match_function_exact: matching a device...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018255#011[D3]
match_function_regex: matching a device...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018263#011[D2] Device
matches
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018266#011[D2] Reading
configuration descriptor 1 of 1
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018272#011[D3]
libusb_kernel_driver_active() returned 0: Success
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018287#011[D2] Claimed
interface 0 successfully
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018291#011[D3]
nut_usb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018298#011[D5]
send_to_all: SETINFO driver.state "reconnect.updateinfo"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.018301#011[D3] send: Q1
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.019481#011[D3] read:
Input/Output Error (-1)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.019496#011[D5]
send_to_all: SETINFO driver.state "reconnect.trying"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.019598#011[D4]
qx_process: failed to preprocess answer [input.voltage]
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.024494#011[D2] Checking
device 1 of 8 (1D6B/0003)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.024507#011[D1] Failed to
open device (1D6B/0003), skipping: Access denied (insufficient permissions)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.024511#011[D2] Checking
device 2 of 8 (17EF/6190)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.024518#011[D1] Failed to
open device (17EF/6190), skipping: Access denied (insufficient permissions)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.024520#011[D2] Checking
device 3 of 8 (17EF/608D)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.024525#011[D1] Failed to
open device (17EF/608D), skipping: Access denied (insufficient permissions)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.024527#011[D2] Checking
device 4 of 8 (0001/0000)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.025734#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.026905#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028052#011[D1]
nut_libusb_open get iProduct failed, retrying...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028057#011[D2] -
VendorID: 0001
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028061#011[D2] -
ProductID: 0000
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028064#011[D2] -
Manufacturer: unknown
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028067#011[D2] -
Product: unknown
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028069#011[D2] - Serial
Number: unknown
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028071#011[D2] - Bus:
003
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028074#011[D2] - Bus
Port: 006
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028076#011[D2] - Device:
006
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028078#011[D2] - Device
release number: 0100
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028081#011[D2] Trying to
match device
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028083#011[D3]
match_function_exact: matching a device...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028085#011[D3]
match_function_regex: matching a device...
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028091#011[D2] Device
matches
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028093#011[D2] Reading
configuration descriptor 1 of 1
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028098#011[D3]
libusb_kernel_driver_active() returned 0: Success
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028111#011[D2] Claimed
interface 0 successfully
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028115#011[D3]
nut_usb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028122#011[D5]
send_to_all: SETINFO driver.state "reconnect.updateinfo"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028125#011[D3] send: Q1
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029292#011[D3] read:
Input/Output Error (-1)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029308#011[D5]
send_to_all: SETINFO driver.state "reconnect.trying"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029395#011[D4]
qx_process: failed to preprocess answer [input.voltage]
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029401#011[D2] Skipping
protocol Ablerex 0.01
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029404#011[D2] Skipping
protocol Q1 0.08
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029407#011Device not
supported!
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029411#011Device not
supported!
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029415#011[D5]
send_to_all: SETINFO driver.state "cleanup.exit"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029420#011[D6]
upsnotify: notify about state 4 with libsystemd: use sd_notify()
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029423#011[D6]
upsnotify: posting sd_notify: STATUS=exit_cleanup()
Dec 19 18:04:56 mustang nut-driver at ups1[916173]: STOPPING=1
Dec 19 18:04:56 mustang systemd[1]: nut-driver at ups1.service: Main process
exited, code=exited, status=1/FAILURE
Dec 19 18:04:56 mustang systemd[1]: nut-driver at ups1.service: Failed with
result 'exit-code'.
Dec 19 18:04:56 mustang systemd[1]: Failed to start nut-driver at ups1.service -
Network UPS Tools - device driver for ups1.
Dec 19 18:04:57 mustang nut-monitor[105815]: Poll UPS [ups1 at localhost] failed
- Driver not connected

Jim Klimov

2025-Dec-19 08:16 UTC

head link

[Nut-upsuser] Digitech support

Thanks,

So on one hand that part does not look too promising:

Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028122#011[D5]
send_to_all: SETINFO driver.state "reconnect.updateinfo"
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.028125#011[D3] send: Q1
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029292#011[D3] read:
Input/Output Error (-1)
Dec 19 18:04:56 mustang nut-driver at ups1[916173]:   0.029308#011[D5]
send_to_all: SETINFO driver.state "reconnect.trying"

but on another, NUT v2.8.2.1 along with `nut_libusb_open get iProduct
failed, retrying` indicates that maybe this is a device with botched
retrieval of language-specific strings, so we get part of that reply and
the rest is seen by USB layer as garbage when asking for Q1. Maybe. At
least, the part about iProduct, iVendor, possibly iSerial was solved about
a year ago - so trying a newer NUT version can help.

Can you please check if you can build the current master branch per
https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests
and run the driver from the resulting build workspace, if that would fare
better? If yes, you can go on about installing that build over the packaged
version; if no, not much of a change for the existing system (except added
build dependency prerequisite packages).

Specifically, I think these PRs can apply to the situation:
* https://github.com/networkupstools/nut/pull/2604 and maybe
https://github.com/networkupstools/nut/pull/2571 (both went into 2.8.3)
* https://github.com/networkupstools/nut/pull/3211 (recently on master,
fixes a string truncation issue possible after #2604 above)

Hope this helps,
Jim Klimov



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

Nut upsuser - Dec 2025 - Digitech support

[Nut-upsuser] Digitech support

[Nut-upsuser] Digitech support

[Nut-upsuser] Digitech support