radiusd only starting with radiusd -X, but not as daemon via rc.freeradius
hello *, 1. i can start radiusd with a valid and working radiusd.config using radiusd -X in this case auth using e.g radtest or other clients is working and stable .. 2. without the -X option and as a "service" via rc.freeradius radiusd will start, but authentication against radius is not sucessful, e.g. using radtest .... ( cannot connect to ... ) as far as i understand, difference between both modes is, that without -X radiusd switches over from root to "user" radius after parsing all config files. So i assume a problem with a socket or else, but with strace i see no hint that gives me a clue any hints in which direction my debugging should go ... ??? System is an openSUSE 10.3 (i586) VERSION = 10.3 SW Package Versions: freeradius-devel-1.1.6-47.4 freeradius-client-1.1.5-36 freeradius-1.1.6-47.4 freeradius-client-libs-1.1.5-36 freeradius-client-devel-1.1.5-36 pam_radius-1.3.16-144 TIA Michael
Michael Arndt wrote:
1. i can start radiusd with a valid and working radiusd.config using radiusd -X in this case auth using e.g radtest or other clients is working and stable ..
2. without the -X option and as a "service" via rc.freeradius radiusd will start, but authentication against radius is not sucessful, e.g. using radtest .... ( cannot connect to ... )
Is the server still running?
as far as i understand, difference between both modes is, that without -X radiusd switches over from root to "user" radius after parsing all config files.
Well... try changing that to see if it helps. Alan DeKok.
Hi,
1. i can start radiusd with a valid and working radiusd.config using radiusd -X in this case auth using e.g radtest or other clients is working and stable ..
2. without the -X option and as a "service" via rc.freeradius radiusd will start, but authentication against radius is not sucessful, e.g. using radtest .... ( cannot connect to ... )
is the process daemon actually running? ps aux | grep radius check the output of the log file (eg /var/log/radiusd/radiusd.log - or wherever your config is set to use) - see whether its a permission issue with a directory or file. alan
participants (3)
-
Alan Buxey -
Alan DeKok -
Michael Arndt