OPNsense Forum

English Forums => General Discussion => Topic started by: kiekar on May 16, 2026, 06:39:04 PM

Title: NUT is Broken After Udating to 26.1.8_5
Post by: kiekar on May 16, 2026, 06:39:04 PM
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

Quote[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>.

Quote<6>[815] pid 76946 (upsc), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
Title: Re: NUT is Broken After Udating to 26.1.8_5
Post by: Patrick M. Hausen on May 16, 2026, 07:16:40 PM
opnsense-revert -r 26.1.7 nut
pkg lock nut
Title: Re: NUT is Broken After Udating to 26.1.8_5
Post by: kiekar on May 16, 2026, 09:32:18 PM
Quote from: Patrick M. Hausen on May 16, 2026, 07:16:40 PMopnsense-revert -r 26.1.7 nut
pkg lock nut

It worked. Thanks