Project

General

Profile

Actions

Bug #1218

closed

Freeradius package does not start when i do reboot

Added by Abdelmonem Abuelezz over 14 years ago. Updated almost 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/20/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

first of all i am not debeloper , i am not sure if this place is the right way to post the bug
Every time i reboot , freeradius did not work unless i do one one of the follound
1- from ssh i do cmmand radiusd s
2
from gui , i change the freeradius listening port and click save

Actions #1

Updated by Brian G about 14 years ago

I am running the FEB 7th Beta5 build. Free radius starts, and the services page confirms this. However, it seems that pfsense may try to start freeradius more than once since clients can no longer authenticate correctly once the system is rebooted after the initial package installation. The log file reads as follows:

"Error: There appears to be another RADIUS server running on the authentication port 1812"

Essentially, you can't reboot pfsense once you install freeradius, otherwise it will no longer work.

Actions #2

Updated by Alexander Wilke over 13 years ago

This bug is stila actual on RC-3.
The webGUI shows freeRADIUS running but clients cannot authenticate anymore. This is after rebooting/restarting pfsense.

My workaround is:
connecting with ssh and then kill the "radiusd -s" process and then do a service restart over the webGUI.

I think the problem is in freeradius.inc because the process there is killed only with "killall radiusd -s" and this is not working when I am using this command on the shell (it is the same command which the stop button under services is using - and not working).
it is only working with "kill -9 <PID>".
Perhaps we should use the kill command from squid package which is using "grep" and "awk" to focus on the correct PID.

Actions #3

Updated by Chris Buechler over 13 years ago

  • Status changed from New to Feedback
Actions #4

Updated by Jim Pingle almost 13 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF