Summary: | Freeradius not starting: libssl version mismatch | ||
---|---|---|---|
Product: | IPFire | Reporter: | datamorgana <datamorgana> |
Component: | --- | Assignee: | Michael Tremer <michael.tremer> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | Crash | ||
Priority: | Will only affect a few users | CC: | adolf.belka, michael.tremer |
Version: | 2 | ||
Hardware: | x86_64 | ||
OS: | Unspecified |
Description
datamorgana
2024-02-15 16:26:02 UTC
Can you try to back up your configuration, uninstall the package and install it again, please? @Michael If freeradius is linked to openssl then presumably freeradius has to have its PAK_VER bumped and be shipped with the core update. If my understanding is correct then I can do a patch submission to bump and ship freeradius for CU184. Yes, this would be the fix. A reinstall would confirm that. I forgot to mention that it would be a good idea to empty the package cache in /var/cache/pakfire before install. What do I have to do to reinstall only the patched freeradius package? Can I leave IPFire as it is and do only a reinstall of freeradius? Will the freeradius configuration be affected/deleted? (In reply to datamorgana from comment #4) > Will the freeradius configuration be affected/deleted? It should be automatically be backed up, but just to be sure, have a backup. > What do I have to do to reinstall only the patched freeradius package? > Can I leave IPFire as it is and do only a reinstall of freeradius? Yes, you only need to reinstall the freeradius package. Thanks! And how will I receive notice of the newly updated freeradius package? Will it be listed in Packfire's "Available Updates" after a click on "Refresh List" while still having not uninstalled the package, or do I need to uninstall the package first and "Refresh List" or just wait? (In reply to Michael Tremer from comment #3) > Yes, this would be the fix. A reinstall would confirm that. > > I forgot to mention that it would be a good idea to empty the package cache > in /var/cache/pakfire before install. # ls -la freeradius* -rw-r--r-- 1 root root 2403485 Nov 18 2020 freeradius-3.0.21-12.ipfire -rw-r--r-- 1 root root 2403944 Mar 28 2021 freeradius-3.0.21-13.ipfire -rw-r--r-- 1 root root 1925542 Oct 25 2021 freeradius-3.0.23-14.ipfire -rw-r--r-- 1 root root 1946169 Nov 4 2022 freeradius-3.0.23-15.ipfire -rw-r--r-- 1 root root 1945708 Mar 7 2023 freeradius-3.0.23-16.ipfire -rw-r--r-- 1 root root 1969214 Jun 17 2023 freeradius-3.0.26-17.ipfire -rw-r--r-- 1 root root 1975527 Jul 19 2023 freeradius-3.0.26-18.ipfire -rw-r--r-- 1 root root 1999033 Oct 13 16:49 freeradius-3.2.3-19.ipfire All of them, or just freeradius-3.0.21-12.ipfire? (In reply to datamorgana from comment #7) > (In reply to Michael Tremer from comment #3) > All of them, or just freeradius-3.0.21-12.ipfire? Sorry, I meant the latest, freeradius-3.2.3-19.ipfire but it would probably safe to just delete all. All is fine. The older ones won't be used anyways. freeradius patch with incremented PAK_VER has been submitted. https://lists.ipfire.org/hyperkitty/list/development@lists.ipfire.org/thread/7MP72LCWTEXMU3NQW63XNHQY7R46STWX/ https://patchwork.ipfire.org/project/ipfire/patch/20240215204757.3824207-1-adolf.belka@ipfire.org/ Merged into master. I did a successful re-install of the addon freeradius-3.2.3-19. Tests with the patched freeradius were also successful. Thanks a lot! I will set the issue to CLOSED / FIXED. |