2.4.3-RELEASE-p1 FreeRADIUS Crash
-
Hi everyone
Edit i have updated the information:
I have noticed that every time my WAN ip address changes FreeRADIUS service stops and does not restart.
I originally thought that Dynamic DNS might of been causing the issue however i believe this not to be true.
I have to manually restart FreeRADIUS service.
My Wan configuration:
Wan link type is PPPoE
Vlan on the wan interface with vlan tag id 2 and Priority is 0
Username and password
Using link interface that was configured with Vlan tag id 2Is anyone else having the same issue?
Is this a known bug? -
This is what I am seeing in the logs just when freeRADIUS crashes
Jul 18 22:39:04 radiusd 15726 [/usr/local/etc/raddb/mods-config/attr_filter/access_reject]:11 Check item "FreeRADIUS-Response-Delay" found in filter list for realm "DEFAULT".
Jul 18 22:39:04 radiusd 15726 [/usr/local/etc/raddb/mods-config/attr_filter/access_reject]:11 Check item "FreeRADIUS-Response-Delay-USec" found in filter list for realm "DEFAULT". -
Hi,
About these 2 lines ;@bigbird007 said in 2.4.3-RELEASE-p1 FreeRADIUS Crash:
Jul 18 22:39:04 radiusd 15726 [/usr/local/etc/raddb/mods-config/attr_filter/access_reject]:11 Check item "FreeRADIUS-Response-Delay" found in filter list for realm "DEFAULT".
Jul 18 22:39:04 radiusd 15726 [/usr/local/etc/raddb/mods-config/attr_filter/access_reject]:11 Check item "FreeRADIUS-Response-Delay-USec" found in filter list for realm "DEFAULT".See http://lists.freeradius.org/pipermail/freeradius-users/2015-October/080219.html
-
Thanks Gertjan
I take it the two lines that i posted has nothing to do with the issue i am facing.
I have been doing a little more testing.
I have disabled dynamic dns , I then forced my wan connection to get a new ip from isp.
I can rule out dynamic dns as the problem still persists with it been disabled.
My Issue is definitely related to when the WAN IP changes.
As a band aid solution i have installed the service Watchdog and have it monitor the radiusd service and to restart it when it stops.
