NUT is Broken After Udating to 26.1.8_5

[kiekar]

Hello,

I just updated OPNsense to 26.1.8_5 from 26.1.6 and noticed the dashboard widget for NUT shows a message "Nut is not returning a status".

I went to System -> Nut -> Diagnostic and noticed the UPS Status page is empty. I'm currently runing the os-nut plugin version 1.9_1.

Below are the general and backend logs. Any help would be much appreciated.

Thanks

[b5ba2e74-de5c-4ea7-9fad-8954797db051] Script action failed with Command '/usr/local/bin/upsc 'apc@127.0.0.1'' died with <Signals.SIGSEGV: 11>. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 93, in execute subprocess.run(script_command, env=self.config_environment, shell=True, ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ check=not self.disable_errors, stdout=output_stream, stderr=error_stream) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/subprocess.py", line 577, in run raise CalledProcessError(retcode, process.args, output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/bin/upsc 'apc@127.0.0.1'' died with <Signals.SIGSEGV: 11>.

<6>[815] pid 76946 (upsc), jid 0, uid 0: exited on signal 11 (no core dump - bad address)

[Patrick M. Hausen]

Code Select Expand

opnsense-revert -r 26.1.7 nut
pkg lock nut


[kiekar]

Code Select Expand

opnsense-revert -r 26.1.7 nut
pkg lock nut


It worked. Thanks

[BurningBarrier]

I just got a UPS that has USB output and was setting it up and I have the same blank diagnostic screen and errors in the backend logs.

running the revert and lock didn't seem to fix the errors or cause the diagnostic screen to work.

[franco]

Instead of a dozen reports for OPNsense I think one to NUT may make a lot more sense:

https://github.com/networkupstools/nut/issues

FreeBSD ports doesn't appear to have any reports or movement on that particular subject.


Cheers,
Franco

[ubu]

Code Select Expand

opnsense-revert -r 26.1.7 nut
pkg lock nut


this fixed my issue as well. THANKS!!! Interesting when trying to figure out why my NUT status was no longer working, Claude informed me that a UI bug has been around since 2021. Not sure if that's related or what but thanks for this temp fix anyway.

[lmoore]

FreeBSD ports doesn't appear to have any reports or movement on that particular subject.

It appears in FreeBSD 14.3 & 15.0 installations, NUT version 2.8.4 gets installed.

- FreeBSD freebsd-14a 14.3-RELEASE-p14 FreeBSD 14.3-RELEASE-p14 GENERIC amd64
- FreeBSD freebsd-15a 15.0-RELEASE-p9 FreeBSD 15.0-RELEASE-p9 releng/15.0-n281048-6d536196f1bd GENERIC amd64

[Dean E. Weimer]

I don't think this is a nut issue, but something more specific on the OPNsense pkg. I am running mine in net client mode with a FreeBSD actually connected to the UPS. That FreeBSD server is running NUT installed from a local Poudriere build with version 2.8.5_1. The server is working without issue.
root@supermicro:/ # pkg info nut-2.8.5_1
nut-2.8.5_1
Name           : nut
Version        : 2.8.5_1
Installed on   : Wed May 27 06:48:15 2026 CDT
Origin         : sysutils/nut
Architecture   : FreeBSD:15:amd64
Prefix         : /usr/local
Categories     : sysutils
Licenses       : GPLv3+, GPLv2+, ART10, GPLv1+
Maintainer     : cy@FreeBSD.org
WWW            : https://www.networkupstools.org/
Comment        : Network UPS Tools

[franco]

I think it's universally accepted that 2.8.3 wasn't broken for anyone. Now there's an update and it's no longer working.

There's also https://github.com/opnsense/plugins/pull/5469 but it also points into a behavioural change of nut for better or worse.


Cheers,
Franco

[RAT]

Code Select Expand

opnsense-revert -r 26.1.7 nut
pkg lock nut


Thank you!

[JediFonger]

opnsense-revert -r 26.1.7 nut
Fetching nut.pkg: ..[fetch: https://pkg.opnsense.org/FreeBSD:15:amd64/26.7/MINT/26.1.7/latest/Latest/nut.pkg.sig: Not Found] failed

[Patrick M. Hausen]

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

[lmoore]

FreeBSD ports doesn't appear to have any reports or movement on that particular subject.

Hmm, I installed FreeBSD 15.1 using the package method a couple of weeks ago and then installed NUT. The version it installed is 2.8.4, just like it did with FreeBSD 14.3 with the latest P version which was installed on the machine just prior 15.1 being installed.

It's unclear how to get NUT 2.8.5 to install as a package on the generic FreeBSD OS installations.

[Patrick M. Hausen]

It's unclear how to get NUT 2.8.5 to install as a package on the generic FreeBSD OS installations.

Did you try changing the package repo from "quarterly" to "latest"?

[franco]

Well, https://www.freshports.org/sysutils/nut says nut is at 2.8.5 at the moment. If they don't push the latest to their repo I don't know why other than it wasn't built in a while.

> Did you try changing the package repo from "quarterly" to "latest"?

Ah, yes, good catch.