Hello,I just installed FreeRADIUS from the networkradius/freeradius repo and tried to start the radiusd service and it failed - Jul 30 17:06:19 d1xradiusadm01 radiusd[54302]: libssl version mismatch. built: 30000070 linked: 30200020 I am running CentOS Stream 9. I've looked up some stuff and found that I can change the LD_LIBRARY_PATH but haven't tried that because i'm not sure if it will work for this. Any help? Thank you
On Jul 31, 2024, at 12:59 PM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Hello,I just installed FreeRADIUS from the networkradius/freeradius repo and tried to start the radiusd service and it failed - Jul 30 17:06:19 d1xradiusadm01 radiusd[54302]: libssl version mismatch. built: 30000070 linked: 30200020 I am running CentOS Stream 9. I've looked up some stuff and found that I can change the LD_LIBRARY_PATH but haven't tried that because i'm not sure if it will work for this.
Different versions of OpenSSL aren't really compatible. As a result, when the server starts, it checks if the version from when it was compiled is the same as what is currently being used. If they're different, the server complains. The packages we provide are linked against OpenSSL 3.0. When you install them, the packaging system should ensure that the packages are using OpenSSL 3.0. In this case, it looks like something on your system broke. i.e. despite being asked to use OpenSSL 3.0, the local OS is truing to use OpenSSL 3.2. That's a problem. The solution is to either install OpenSSL 3.0 and have FreeRADIUS use that, or build a local copy of FreeRADIUS which is linked to OpenSSL 3.2. Alan DeKok.
The packages we provide are linked against OpenSSL 3.0. When you install them, the packaging system should ensure that the packages are using OpenSSL 3.0. In this case, it looks like something on your system broke.
Would it be possible to link the library statically to prevent the mixups? I know it would raise the binary size, but it could solve these problems. Ludo
On Aug 16, 2024, at 2:11 PM, Ľudovít Mikula <ludovit.mikula@mikori.sk> wrote:
The packages we provide are linked against OpenSSL 3.0. When you install them, the packaging system should ensure that the packages are using OpenSSL 3.0. In this case, it looks like something on your system broke.
Would it be possible to link the library statically to prevent the mixups? I know it would raise the binary size, but it could solve these problems.
That's not really an option, unfortunately. Alan DeKok.
participants (3)
-
Alan DeKok -
Andrew Meyer -
Ľudovít Mikula