"
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
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
