Unbound reporting stop working

[wincent]

I have upgraded OPNsense from 26.1.8 to 26.1.9 yesterday, the Unbound Reporting shows empty, Reset DNS data doesn't help, then I checked the Backend logs, it shows error:

Code Select Expand

2026-06-11T12:58:34Errorconfigd.py[200067b7-b4a7-4c0d-9581-d445d8562592] Script action failed with Command '/usr/local/opnsense/scripts/unbound/stats.py totals --max '10'' died with <Signals.SIGILL: 4>. 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/opnsense/scripts/unbound/stats.py totals --max '10'' died with <Signals.SIGILL: 4>.and then I try to run stats.py on Console, it returns:

Code Select Expand

#/usr/local/opnsense/scripts/unbound/stats.py details --limit 1000
Illegal instruction
My hardware platform is Checkpoint 4600 with Pentium(R) Dual-Core CPU E6500 and 4G RAM.

[franco]

Could be the switch to py-numpy 1.x -> 2.x. It would indicate your CPU is now too old to run it.


Cheers,
Franco

[wincent]

That's reason!
It seems that I can only disable the Unbound reporting for now.

[franco]

Yes, sorry about that. The bright side of it was NumPy 2.0 is about 2 years old now and FreeBSD ports prolonged the life of 1.x for that long already.


Cheers,
Franco

[wincent]

I appreciate all work you have done on OPNsense.
I am attempting to send Unbound's logs to the syslog server.

Thanks again!

[franco]

Apprently this made some waves looking at https://github.com/freebsd/freebsd-ports/commit/3c11b048c3d -- in theory we could flip it back but I'll have to discuss internally. The minimum optimization requirement was probably done for a good reason.


Cheers,
Franco

[wincent]

I'm glad to hear this.
It's a tough decision. After all, OPNSense focuses on security performance, and Unbound DNS reporting is just a plug-in functional component. However, many firewall platforms or all-in-one servers may not be equipped with the latest CPU, and I believe many users still require this functionality.

Thanks!

[nero355]

Apprently this made some waves looking at https://github.com/freebsd/freebsd-ports/commit/3c11b048c3d -- in theory we could flip it back but I'll have to discuss internally. The minimum optimization requirement was probably done for a good reason.

I'm glad to hear this.
It's a tough decision. After all, OPNSense focuses on security performance, and Unbound DNS reporting is just a plug-in functional component. However, many firewall platforms or all-in-one servers may not be equipped with the latest CPU, and I believe many users still require this functionality.

It was not exactly easy to find, but I guess you could check this : https://numpy.org/doc/stable/user/troubleshooting-importerror.html#segfaults-or-crashes

And compare it to this : https://www.techpowerup.com/cpu-specs/pentium-e6500.c864
_{Found via https://duckduckgo.com/?q=Pentium(R)+Dual-Core+CPU+E6500}

But if I am perfectly honest I can't really blame the guys for excluding such old CPU models : The days of Socket 775 are waaaay behind us now! :)
Looking at other software that had similar changes over the last 5 years or so I would recommand having at least something with AVX support for regular CPUs and I believe it was SSE4 for the Atom-like models.

Considering the horrible hardware prices situation we are currently in maybe you could look at used hardware that's in good condition as an upgrade option ?!