Crash when connect to remote NUT server

[vatprcyq]

Please make sure to fill out this form completely, and attach your program logs (set to Debug setting). You can delete this line.

• [ √] Searched to see if this issue exists
• [ √] Completed below form
• [ √] Attached debug log file
• Copy output in File -> UPS Variable ---can't open this

**WinNUT Version: ** 2.2.8719.24624
**Windows OS Version: ** Windows 11 Build 27863

Describe the bug
Show connected and program crashed.

To Reproduce
Steps to reproduce the behavior:

1. Exec program
2. Popup connected
3. Show Error Dialog and program crashed
4. See error

Expected behavior
Connected and normal showing data from UPS
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Crash report:

CrashReport_2025-05-27T16.24.58.txt

[gbakeman]

Hello,

It looks like this may be a duplicate of #129. Please update to Pre-Release v2.3.8824 or later to apply the fix. Let me know here if that works for you.

[vatprcyq]

Hello,

It looks like this may be a duplicate of #129. Please update to Pre-Release v2.3.8824 or later to apply the fix. Let me know here if that works for you.

It works with latest pre-release v2.3.8988
But remaining time shows invaild.

WinNUT-Client-2025-05-29.log

[gbakeman]

The first thing I want to call out is Pre-Release v2.3.8824, specifically issue #116 which addresses how WinNUT originally handled invalid UPS data. Before, if WinNUT received invalid data during a variable query (such as non-existent or out of range), WinNUT would then set the variable to a realistic-looking or nominal default value and use that going forward. After that update however, I made it so that WinNUT no longer does this and maintains a variable at obvious invalid values (0 or -1 for example) when there's an error encountered querying it.

I'm curious if you've ever been able to retrieve data successfully from the NUT server/UPS before? Looking through your log file, I see lots of errors when WinNUT tries to query the server for variable information, which indicates to me that there may be an issue on the server side. Can you try going to the File menu, and get the variables list for the UPS?

[vatprcyq]

ups (Unknown/Unknown/Unknown)
battery.voltage (Battery voltage (V)) : 2.26
device.type (Description unavailable) : ups
driver.name (Driver name) : nutdrv_qx
driver.parameter.pollfreq (Description unavailable) : 30
driver.parameter.pollinterval (Description unavailable) : 2
driver.parameter.port (Description unavailable) : /dev/mizuki
driver.parameter.synchronous (Description unavailable) : auto
driver.version (Driver version - NUT release) : 2.8.0
driver.version.data (Description unavailable) : Q1 0.07
driver.version.internal (Internal driver version) : 0.32
driver.version.usb (USB library version) : libusb-1.0.26 (API: 0x1000109)
input.frequency (Input line frequency (Hz)) : 50.3
input.voltage (Input voltage (V)) : 240.5
input.voltage.fault (Description unavailable) : 220.0
output.voltage (Output voltage (V)) : 205.2
ups.beeper.status (UPS beeper status) : disabled
ups.delay.shutdown (Interval to wait after shutdown with delay command (seconds)) : 30
ups.delay.start (Interval to wait before (re)starting the load (seconds)) : 180
ups.load (Load on UPS (percent of full)) : 10
ups.status (UPS status) : OL
ups.temperature (UPS temperature (degrees C)) : 30.0
ups.type (UPS type) : online

[gbakeman]

I think this confirms that the NUT server is only providing some basic monitoring info then. This is a strange UPS to me, I don't think I've seen that driver before. You may want to refer to the Network UPS Tools support for further troubleshooting to see if you can get any additional info out of your UPS.