NUT is Broken After Udating to 26.1.8_5

[lmoore]

try changing the package repo from "quarterly" to "latest"

Thanks Patrick, I'll try that when the test machines are freed from their current role.

Cheers,

Larry.

[JediFonger]

yes:
OPNsense 26.7-amd64
FreeBSD 15.1-RELEASE-p1
OpenSSL 3.5.7

Are you on 26.7? In that case this workaround is not necessary, anymore.

i was able to install 1.8.5 manually:
pkg install nut-2.8.5_1

pkg info|grep -i nut
nut-2.8.5_1                    Network UPS Tools

^but issue remains, not sure how to proceed. guess i gotta keep waiting?

[Patrick M. Hausen]

The NUT release bundled with OPNsense 26.7 is current and working:

Code Select Expand

root@opnsense:~ # opnsense-version
OPNsense 26.7 (amd64)
root@opnsense:~ # pkg info | grep nut
nut-2.8.5_1                    Network UPS Tools
os-nut-1.9_1                   Network UPS Tools

What issue exactly are you seeing?

[JediFonger]

monitor service runs,tool doesn't. on gui when i click on nut, i get the bug report crash.

also, apcupsd status is 'commlost' very odd.

The NUT release bundled with OPNsense 26.7 is current and working:

Code Select Expand

root@opnsense:~ # opnsense-version
OPNsense 26.7 (amd64)
root@opnsense:~ # pkg info | grep nut
nut-2.8.5_1                    Network UPS Tools
os-nut-1.9_1                   Network UPS Tools

What issue exactly are you seeing?

[Patrick M. Hausen]

on gui when i click on nut, i get the bug report crash.

That's a new OPNsense frontend problem completely unrelated to the NUT crash we had on 26.1 and definitely not fixed by manually messing around with packages.

Rather, just do:

Code Select Expand

opnsense-patch https://github.com/opnsense/core/commit/14710e775

The crash report you get looks nowhere like the issue we had on 26.1 yet somehow you come to the conclusion that both issues are the same and require the same fix? The title of this thread is "NUT is Broken After Udating to 26.1.8_5". Not "NUT is Broken After Udating to 26.7".  🤷

If you installed the workaround on 26.1 then unlock the NUT package:

Code Select Expand

pkg unlock nut

Then check for pending updates from the UI and update the NUT package to the one matching 26.7. Then apply the patch above.

[error01]

This is a known upstream issue where the upsc binary segfaults on process exit under the updated NUT version, preventing configd from returning diagnostic data to the WebUI. As a temporary workaround, you can downgrade the package via CLI using opnsense-revert -r 26.1.7 nut or monitor performance analytics via https://www.yepapi.com/ until an official patch is released.

[Patrick M. Hausen]

This known upstream issue is only present on OPNsense 26.1. A crash report in the UI as seen on 26.7 is a completely different thing. Please stop mixing the two issues all the time. The solution to the 26.7 issue is to apply the patch in my last post.

[JediFonger]

that fixed it, thank yOU!

on gui when i click on nut, i get the bug report crash.

That's a new OPNsense frontend problem completely unrelated to the NUT crash we had on 26.1 and definitely not fixed by manually messing around with packages.

Rather, just do:

Code Select Expand

opnsense-patch https://github.com/opnsense/core/commit/14710e775

The crash report you get looks nowhere like the issue we had on 26.1 yet somehow you come to the conclusion that both issues are the same and require the same fix? The title of this thread is "NUT is Broken After Udating to 26.1.8_5". Not "NUT is Broken After Udating to 26.7".  🤷

If you installed the workaround on 26.1 then unlock the NUT package:

Code Select Expand

pkg unlock nut

Then check for pending updates from the UI and update the NUT package to the one matching 26.7. Then apply the patch above.