Freeradius2 problems
-
I've updated to the latest snapshot:
2.2-ALPHA (amd64) built on Wed Jul 16 09:13:49 CDT 2014 FreeBSD 10.0-STABLE
freeradius2 won't run:
Jul 17 09:39:51 pfsense-kvm root: /usr/pbi/freeradius-amd64/etc/rc.d/radiusd: WARNING: /usr/local/etc/raddb is not a directory. Jul 17 09:39:51 pfsense-kvm root: /usr/pbi/freeradius-amd64/etc/rc.d/radiusd: WARNING: failed precmd routine for radiusd
Does anybody have the same problem or knows how to fix it?
-
I took a look at the config file and found the problem. On my AMD64 test installation there's a wrong path in:
/usr/pbi/freeradius-amd64/etc/rc.d/radiusd
# The radiusd_config parameter is now obsolete. Instead, derive the # configuration directory name from radiusd_flags if possible, otherwise # default to [b]/usr/local/etc/raddb[/b] required_dirs=`echo ${radiusd_flags} | sed -Ene 's:.*\-[^[:space:]d]*d[[:space:]]*([^[:space:]]+).*:\1:p'` required_dirs=${required_dirs:-"/usr/local/etc/raddb"}
I guess that config might be auto generated at some point, because on a 2.1 install it looks like this:
# The radiusd_config parameter is now obsolete. Instead, derive the # configuration directory name from radiusd_flags if possible, otherwise # default to /usr/pbi/freeradius-amd64/etc/raddb required_dirs=`echo ${radiusd_flags} | sed -Ene 's:.*\-[^[:space:]d]*d[[:space:]]*([^[:space:]]+).*:\1:p'` required_dirs=${required_dirs:-"/usr/pbi/freeradius-amd64/etc/raddb"}
Changing the last "required_dirs" line on my 2.2 install like this:
required_dirs=${required_dirs:-"/usr/pbi/freeradius-amd64/etc/raddb"}
makes freeradius2 start again.
It complains about an SSL mismatch, though:Aug 25 14:00:16 radiusd[1630]: libssl version mismatch. Built with: 1000107f Linked: 1000109f Aug 25 14:00:18 radiusd[1630]: Loaded virtual server <default> Aug 25 14:00:18 radiusd[15010]: Ready to process requests.</default>
Maybe someone can fix the package with my findings?
-
libssl version mismatch is fixed here: https://redmine.pfsense.org/issues/3816
-
Hi charliem,
thanks for the info, did you try that on your system and does it work without problems?
I just installed a fresh AMD64 2.2 alpha, got the latest freeradius2 package and it still has that error:radiusd[20619]: libssl version mismatch. Built with: 1000107f Linked: 1000109f
-
thanks for the info, did you try that on your system and does it work without problems?
No, I didn't, just saw an entry in the activity log. I see the bug is now reopened, and points to your post. Thanks for testing!
-
Same problem here (pfsense 2.1.5 64Bit):
radiusd[97710]: libssl version mismatch. Built with: 90819f Linked: 9081bfI read this advice https://redmine.pfsense.org/issues/3816 but not sure what to do?! Could somebody help me / us?
Thanks..
-
Please try last package version.
-
Thanks for looking into this, we're half way there now :)
No more libssl errors on my 64Bit beta, but it still does not start without my manual config file tweaks mentioned some posts before. Error is still the same:
Sep 26 15:18:44 root: /usr/pbi/freeradius-amd64/etc/rc.d/radiusd: WARNING: /usr/local/etc/raddb is not a directory. Sep 26 15:18:44 root: /usr/pbi/freeradius-amd64/etc/rc.d/radiusd: WARNING: failed precmd routine for radiusd
-
Please try package version 1.6.9
-
Great, thank you very much for your support! This looks fine, everything working as expected now as far as I can tell.
-
Problem solved with newest Package Version.
-
Problem solved with newest Package Version.
Not for me:
Nov 6 15:11:19radiusd[67453]: libssl version mismatch. Built with: 90819f Linked: 9081bf
2.1.12_1/2.2.5_3 pkg v1.6.10
I even reinstalled, but it gives the error.
-
I have the same Problem:
radiusd[45708]: libssl version mismatch. Built with: 90819f Linked: 9081bf
PF Vesion: 2.1.5-RELEASE (amd64)
Freeradius2: 2.1.12_1/2.2.5_3 pkg v1.6.10
Is there a workaround for this Problem?
Thanks
-
Same problem here.
libssl version mismatch. Built with: 90819f Linked: 9081bffreeradius2 2.1.12_1/2.2.5_3 pkg v1.6.10
pfSense 2.1.5-RELEASE (amd64) -
This thread is for 2.2, not 2.1.5. Different binaries. If you have that error on 2.1.5, start a new thread in the packages forum rather than using this unrelated thread.