[SOLVED] Freeradius doesn't start after a pfsense 2.4.4 fresh install and restored previous config.

dddave

Hi all,

I just upgraded freeradius3 package to version 0.15.5_4 running on APU hardware with pfsense build: 2.4.4-RELEASE.

It's been running pretty much rock solid for years... (should not have upgraded! :( ).

I need guidance on where to look to help diagnose this please??? :(

Previously after the last update I had to manually re-start after a boot up -> now I cannot manually start, and I cannot see any logs in the radius.log file under /var/log? No errors in any of the system logs. Is this a temporary issue that anyone is aware of? Its been pretty rock stable until now. Re-installation of the package / changing a few settings or rolling config back config has not helped. Cannot get the service to boot. Does this ring any bell's / idea's from anyone? Luckily it only handles Wireless authentication, so we have 1 SSID I can use that is rate limited that doesn't use it - so the family "may not notice" - but I'm a tad surprised as I know some big names use PFSense, for various elements.

Where may I find more log information to help break the root cause down?

Thanks in advance - please link to other posts if I couldn't find them - or advise if this is already know / in pending merges.

David

dddave

And yes - sorry I know the package is third party - please advise where to post if this is not suitable - but it doesn't help the brand, as many consumers will see it as part of the PFSense brand.

juruteknik

hi dddave, please share the output of radiusd -X

i have same problem here

strangegopher

Same issue here.

radiusd -X show:

Errors reading /usr/local/etc/raddb/dictionary: dict_init: /usr/local/etc/raddb/dictionary[6] invalid entry

/usr/local/etc/raddb/dictionary :

# Local dictionary, does not need to include the master dictionary
ATTRIBUTE               MOTP-Init-Secret                900     string
ATTRIBUTE               MOTP-PIN                        901     string
ATTRIBUTE               MOTP-Offset                     902     string

 /usr/share/doc/radius/dictionary.pfsense

edit: removing the last line fixes the issue. also changing the last line to be this works

$INCLUDE /usr/share/doc/radius/dictionary.pfsense

Now a reboot will remove this fix.

edit2: created bug report - https://redmine.pfsense.org/issues/8989

RikkertJ

@strangegopher that seems to resolve the issue. Thank you!

sisko212

@strangegopher I can confirm your workaround. This fix the issue.

free4

@dddave @juruteknik @strangegopher @RikkertJ and @sisko212
I appologize for this problem, this is my fault. I am an occasional contributor to pfSense and it's me who caused this issue.

I submited a pull request to fix the issue ( https://github.com/pfsense/FreeBSD-ports/pull/579 ). I hope it will be merged fast.

Gertjan

@strangegopher said in [SOLVED] Freeradius doesn't start after a pfsense 2.4.4 fresh install and restored previous config.:

Same issue here.
edit: removing the last line fixes the issue. also changing the last line to be this works
$INCLUDE /usr/share/doc/radius/dictionary.pfsense
Now a reboot will remove this fix.
edit2: created bug report - https://redmine.pfsense.org/issues/8989

Edit (only) this file : /usr/local/pkg/freeradius.inc
Line 3666
Change

$INCLUDE /usr/share/doc/radius/dictionary.pfsense

for

\$INCLUDE /usr/share/doc/radius/dictionary.pfsense

Escaping the $ (adding a backslash in front) and "$INCLUDE" will be included literally.
Now the patch will persists after rebooting.

Btw : to apply the edit : reboot !

edit : @free4 : look at the source, it's just the backslash that is missing. Instead of reverting your PL, add another PL and done ^^

jimp

This should be fixed in the latest version of the pkg now

Gertjan

Yep, installed the ...5 : case closed.