Freeradius 2 doesn't start after upgrade to PFS 2.2
-
Going to the next request
Ready to process requests.Looks like it starts to me.
-
Yes it did and it does. Wen I (re)start the PFS box Freeradius is not starting. I have to click the save button then it starts right away. I don't have to change any of the settings just click the save button in the settings UI is enough to start Freeradius but it doesn't start after a reboot of the system. Wen I stop freeradius in the PFS web GUI and start it on the ssh command line with radiusd -X it also runs normal.
See https://forum.pfsense.org/index.php?topic=87441.msg480196#msg480196
and https://forum.pfsense.org/index.php?topic=87441.msg487188#msg487188 -
After restart Pfsense 2.2.1 freeradius not starting. If button SAVE on Services:FreeRADIUS: Interfaces or Services:FreeRADIUS: Setting (WebGui) then Starting. How to solve the automatic start? Reinstall/Uninstall does not solve the problem, if there is a reboot.
-
i think it might be best to create a bugreport for this.
instead of clicking "save' , have you tried restarting the service manually ? (status–>services)If that works, then you might be able to get it running automatically by temporarily installing the "service watchdog" package and having it monitor the freeradius service.
-
Are these full installs or nanobsd installs that are having this issue?
I can reproduce that same error message by deliberately corrupting db.daily file, but once I do that saving FreeRADIUS config pages does not solve the problem. Are you guys deleting the file before saving settings?
-
Full symmetric multiprocessing kernel install.
In my case, it is several months between the db.daily corruptions.I delete the file and do not touch any settings.
-
@G.D.:
Full symmetric multiprocessing kernel install.
In my case, it is several months between the db.daily corruptions.I delete the file and do not touch any settings.
That's interesting, so it does not happen every time you restart FreeRADIUS, but sometimes. Do you use 'Amount of Time' feature under Users tab?
It might help if someone uploaded corrupt db.daily file here. -
That is another user that has it happening on every restart.
In my case it is very long time between corruptions. Though I have very few restarts.I can tell you that in my case the corrupted db.daily is smaller than a good one.
Corrupted: 16 KiB
Good: 64 KiBI do not use the "Amount of Time" feature.
-
All counter files on my system are 128 KiB. Can you upload your good file, I will compare the two. I have been running FreeRADIUS package since 2.0 RC days and never experienced this issue.
-
With me the problem is mysql56, freeradius2 can´t start after boot but works ok manually starting service after boot.
radiusd[84593]: rlm_sql_mysql: Couldn't connect socket to MySQL server radius@localhost:radiusI´m looking for for a way to delay freeradius2 service to start, I think in this way mysql will be ready for new connections before freeradius starts.
-
New version of FreeRADIUS package 1.6.11 fixes the issue of multiple radiusd instances being launched (see: https://redmine.pfsense.org/issues/4337). It is a long shot that that will resolve your problem, but please upgrade and report back. You do need to remove/install package rather than reinstall for the changes to appear on your system. If the update is installed correctly you should see below lines in /usr/local/etc/rc.d/radiusd.sh
... rc_start() { SERVICENAME="radiusd" LOCKFILE="/tmp/${SERVICENAME}_start.lock" PIDFILE="/var/run/${SERVICENAME}.pid" ... -
FreeRadius 2.2.6_3 pkg v1.6.11 Pfsense 2.2.1. remove/install package. The problem is not solved. How to remove a second copy of the program (The FreeRADIUS daemon)? After removal pkg it remains in line "service"
Log:
rlm_counter: Failed to open file /var/log/radacct/timecounter/db.daily: No such file or directory
radiusd[88428]: /usr/local/etc/raddb/modules/counter[71]: Instantiation failed for module "daily"/usr/local/etc/rc.d/radiusd.sh –>
....
rc_start() {
SERVICENAME="radiusd"
LOCKFILE="/tmp/${SERVICENAME}_start.lock"
PIDFILE="/var/run/${SERVICENAME}.pid"
....
-
Removing the package does not remove "/var/log/radacct/timecounter/db.daily" so delete the file manually and try to start FreeRADIUS.
-
Here also installed the update and rebooted and after that powered off the box and restarted but in both restarts the problem is not solved.
-
Can't reproduce this issue, so unless you guys can post additional info that might help in identifying this problem, this is not going get solved.
As a work around you can probably modify startup script '/usr/local/etc/rc.d/radiusd.sh' to remove corrupt file before every start.
-
Dears,
The problem appeared only when I do restore a full backup & the box reboot & re-installing the installed packages…I have tried all work around here with no luck !
in the console it's sayingStarting package freeradius2...done. Starting /usr/local/etc/rc.d/radius.sh...done.but the service is not started & in the log I can find this:
Apr 20 02:58:32 php-fpm[245]: /rc.start_packages: Restarting/Starting all packages. Apr 20 02:58:32 php-fpm[245]: /rc.start_packages: The command '/usr/local/etc/rc.d/radiusd.sh stop' returned exit code '1', the output was 'radiusd not running?' Apr 20 02:58:32 php-fpm[245]: /rc.start_packages: The command '/usr/local/etc/rc.d/radiusd.sh stop' returned exit code '1', the output was 'radiusd not running?' Apr 20 02:58:32 php-fpm[245]: /rc.start_packages: The command '/usr/local/etc/rc.d/radiusd.sh stop' returned exit code '1', the output was 'radiusd not running?' Apr 20 02:58:32 php-fpm[245]: /rc.start_packages: The command '/usr/local/etc/rc.d/radiusd.sh stop' returned exit code '1', the output was 'radiusd not running?' Apr 20 02:58:32 php-fpm[245]: /rc.start_packages: The command '/usr/local/etc/rc.d/radiusd.sh stop' returned exit code '1', the output was 'radiusd not running?' Apr 20 02:58:32 php-fpm[245]: /rc.start_packages: The command '/usr/local/etc/rc.d/radiusd.sh stop' returned exit code '1', the output was 'radiusd not running?' Apr 20 02:58:32 php-fpm[245]: /rc.start_packages: The command '/usr/local/etc/rc.d/radiusd.sh stop' returned exit code '1', the output was 'radiusd not running?'Seems like the box try to stop the service instead of starting it !!!
-
I 've same problem and I can't resolve it :-\ :(
-
I have a fresh pfsense install… with only freeradius & got the error only when restoring the all backup file & the system reboot & reinstalling the packages again...
SOLVED after installing any other package (i.e. squid3 or dansguardian or any other),
if I remove those packages… the problem retains !!! it must have another package installed to start automatically :D :D
-
For my system with regular install (not NanoBSD) and memory file system for /tmp and /var I found a workaround that worked for me in https://forum.pfsense.org/index.php?topic=92636.0.
Still I believe that the problem described is a bug in pfsense/freeradius, which in my case was first introduced when upgrading from 2.2 to 2.2.1 (occasionally no service start at (re)boot). It became even worse (never start at (re)boot) when upgrading to 2.2.2. Note that the in the original clean install of 2.2 freeradius worked flawlessly.
-
Hi;
I experience the exact same issue with a fresh install of pfSense 2.2.2 and freeradius2 1.6.12. Well, not exactly fresh install: I did have to upgrade from pfSense 2.1 as 2.2 does not install correctly on soekris board 6501.The setup is basic with only a connection from RADIUS to a LDAP Active Directory, nothing else installed or configured behond your typically home firewall setup. Service will only start if I save a file on the GUI (no changes necessary) or start manually from command line as described in this post. I notice this now so I have nothing yet to provide in addition to what was already posted.
I'll use the mentioned work around at https://forum.pfsense.org/index.php?topic=92636.0 for now as I need to move on to other priorities but willing to help if some more knowledgeable people can provide pointers or things to try. As mentioned, starting in debug mode provides no additional clue as start-up manually works flawlessly. Errors in system logs are already provided I those are the ones I see.
