On May 26, 2021, at 10:30 AM, Sebastian Hagedorn <Hagedorn@uni-koeln.de> wrote:
We run freeradius on RHEL 7, using our own RPMs that are based on the SPEC file included with freeradius, but with some differences. Our database team doesn’t want to use the stock mariadb RPM, so we use version 10.5 from http://yum.mariadb.org/10.5/rhel7-amd64.
The issue is that I have found that when I build the freeradius 3.0.22 RPM with MariaDB 10.5 installed, the freeradius server doesn’t run properly. I configured a panic_action and can provide the gdb files if there is interest. If I use mariadb-devel 5.5 (standard issue RHEL 7) to build, everything works fine, even when the database server is running MariaDB 10.5. So there is a workaround, but I wonder if it shouldn’t be possible to compile with the newer version installed?
You're building FreeRADIUS against one version of the MariaDB client libraries. Then at run time, linking it to a different version of the MariaDB client libraries. Mixing and matching libraries doesn't usually work well. You should get the mariadb-devel libraries and headers from the same location that you got the run-time libraries from. What's happening is that the internal data structures used by the Mariadb client have one definition on the build system, and then have different definitions on the production system. That cause things to go "boom". Alan DeKok.