Unbound reporting stop working

[sopex]

We don't have much budget. I remember this 4600 cost around $15,000, and now the new 3790 costs around almost $20,000.
I plan to replace it with a spare HP DL388, but there's a problem. The HP server takes too long to boot up, and the self-test takes several minutes, which is quite a headache.

There is also a middle ground between spending $20,000 and wasting time and electricity with a DL388 just to run a firewall.

Official opnsense hardware :)

https://shop.opnsense.com/product/dec3940-opnsense-rack-security-appliance/

[Patrick M. Hausen]

Why buy Checkpoint gear to run OPNsense in the first place?

[wincent]

For reference here is the relevant pull request on GitHub: https://github.com/numpy/numpy/pull/28896

The internal meeting is today. Just so you know I still owe you an answer here.


Cheers,
Franco

I am deeply grateful for your efforts.
Waiting for good news.

[wincent]

Why buy Checkpoint gear to run OPNsense in the first place?

We have been using it because this device can only be upgraded to Gaia 77.30 at most, while OPNsense keeps updating and allows users to customize the required functions(Base on FreeBSD). Therefore, I switched the system to OPNsense and it runs perfectly :)

[Patrick M. Hausen]

Yes, but why even consider buying a new Checkpoint unit? There are many more affordable options for running OPNsense as @sopex already pointed out.

[wincent]

Currently, we have no plans to upgrade this device. If we were to upgrade, I probably wouldn't consider buying a Checkpoint to run OPNsense. As you mentioned, there are many options available.

[nero355]

If we were to upgrade, I probably wouldn't consider buying a Checkpoint to run OPNsense. As you mentioned, there are many options available.

That's also what I meant and not what you seem to have thought in your previous post :

We don't have much budget. I remember this 4600 cost around $15,000, and now the new 3790 costs around almost $20,000.

So this is a nice option too :

I plan to replace it with a spare HP DL388, but there's a problem. The HP server takes too long to boot up, and the self-test takes several minutes, which is quite a headache.

Too bad that it seems to be giving you issues... :(

HPE stuff usually has enough tools to check things so I hope you can find something and solve it without it giving you issues in the future :)

[wincent]

This is not an urgent matter, so anything can be tried. ^-^

[jiggsjedi]

Good morning,

Just adding a reply to track updates here, as I'm facing the same errors on my older rig running an AMD Phenom II 965 BE.

Thanks all.

[erwinvanlonden]

So I guess this falls in the same category. I have Opnsense running in a ProxMox VM and has never been issue until the last update.

The underlying CPU is an Intel Celeron as I don't need OpnSense run a gazillion of sessions and has never had a performance problem. It would be very helpful if we could have this resolved. I know we're depending on an external set of libraries but it's a bit worrisome that parts of the product stop working due to "virtual" restrictions which haven't been a real problem before.

```
vendor_id   : GenuineIntel
cpu family   : 6
model      : 156
model name   : Intel(R) Celeron(R) N5105 @ 2.00GHz
```

[jiggsjedi]

Franco,

Are you able to share any updates here yet?

Thank you

[Rick]

I'm using OPNsense 26.7.7 with py313-numpy 2.4.6_1 on a system with an AMD Athlon 64 X2 5000+ (super old, but runs OPNsense great) and noticed this yesterday when I tried to enable Unbound logging.

Apparently this error happens because recent versions of NumPy are compiled to use features on newer hardware and the complied code chokes on older hardware.  (Google: numpy illegal instruction)  You can see the stack trace by running "python3 -v stats.py"  I tracked the error to the following dynamic-link library:

/usr/local/lib/python3.13/site-packages/numpy/_core/_multiarray_umath.cpython-313.so

I worked around this by standing up a FreeBSD 15.1 VM (on my Linux Mint system), installing Python 3.13 and building NumPy for a generic system using the following command-line, and replacing the OPNsense ".so" above with the one generated (in the same location).

python3 -m pip install numpy==2.4.6 -Csetup-args=-Dcpu-baseline="none" -Csetup-args=-Dcpu-dispatch="none"

Unbound logging is working now on my system.
Obviously this is just a workaround for the current version of NumPy.
Hope this helps.

- Rick

[franco]

The other workaround is not using ancient hardware. Don't feel comfortable pushing generic instructions in 2026 on everyone just because there is still some old hardware around that can't do basic optimizations.


Cheers,
Franco

[nero355]

AMD Athlon 64 X2 5000+ (super old, but runs OPNsense great)

Dude replace that power hungry beast with something like the Intel Atom N100 and be happy :)

IIRC everything newer than the S939 models up to the X2 4600+ was basically DOA because Intel had developed better CPU models in the meantime... Intel Conroe Generation I think...

My S939 X2 4400+ was fun, but I would not use it anymore unless it's for something like "Retro Gaming" or whatever :)

[Rick]

The other workaround is not using ancient hardware. Don't feel comfortable pushing generic instructions in 2026 on everyone just because there is still some old hardware around that can't do basic optimizations.

I get that. :-)  The system was what I had at the time my D-Link DSR-250 got hit with a severe CVE that D-Link flagged as "Won't fix", and it's generally "not broke", and uses commodity hardware, so I'm reluctant to replace it, for now anyway.

I don't know if is applicable, but I've read that the feature-set detection in NumPy can sometimes be incorrect on some hardware, especially AMD, which can cause the "illegal instruction" issue (see link below).  An option might be to compile NumPy with OpenBlas support so the OPENBLAS_CORETYPE environment variable can be used to specify the specific platform.  For example, "OPENBLAS_CORETYPE=Haswell".  I don't think the stock FreeBSD 15 NumPy package has this enabled.  I can't check that on my OPNsense system as NumPy crashes on import. :-)   There are apparently other env-vars that can be set, like "NPY_DISABLE_CPU_FEATURES" (also mentioned below), but I haven't researched them.

NumPy Troubleshooting: Segfaults or crashes
https://numpy.org/doc/stable/user/troubleshooting-importerror.html#segfaults-or-crashes

I don't think any of that will help my system, but might help others.
- Rick