OPNsense Forum

English Forums => 26.1, 26,4 Series => Topic started by: wincent on June 11, 2026, 07:29:53 AM

Title: Unbound reporting stop working
Post by: wincent on June 11, 2026, 07:29:53 AM
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:
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:
#/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.
Title: Re: Unbound reporting stop working
Post by: franco on June 11, 2026, 07:48:23 AM
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
Title: Re: Unbound reporting stop working
Post by: wincent on June 11, 2026, 08:00:37 AM
That's reason!
It seems that I can only disable the Unbound reporting for now.
Title: Re: Unbound reporting stop working
Post by: franco on June 11, 2026, 08:05:22 AM
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
Title: Re: Unbound reporting stop working
Post by: wincent on June 11, 2026, 08:16:08 AM
I appreciate all work you have done on OPNsense.
I am attempting to send Unbound's logs to the syslog server.

Thanks again!
Title: Re: Unbound reporting stop working
Post by: franco on June 11, 2026, 08:27:17 AM
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
Title: Re: Unbound reporting stop working
Post by: wincent on June 11, 2026, 08:43:17 AM
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!