Hello, The failure to start daemon using service radiusd start has the following cause :
* The problem does not occurs with default config. When /etc/init.d/radiusd is launched by init or using service command, it seems environment does not have $ENV{HOSTNAME} initialized. (CentOS 5.4, CentOS 5.5, freeradius 2.1.8-2 or 2.1.9) When I used this in my radiusd.conf to get local site-dependant parameters {listen address, and so on ...), starting radiusd using service command fails ... I solved the problem by initializing hostname variable by including a local.conf site-specific files. Doing son I can rsync configurations between my differents servers, just excluding local.conf in rsync ... So, this is not a freeradius problem. Thanks anyway for you help. Best regards, Fred MAISON Le mercredi 02 juin 2010 à 13:25 -0400, John Dennis a écrit : > On 06/02/2010 12:54 PM, Fred MAISON wrote: > > Hi all, > > Did someone encountered automatic startup at boot-time with freeradius > > 2.1.9-2 on CentOS 5.5 ? > > > > chkconfig --list show OK > > It does say "on" for levels 2,3,4,5 right? > > > /etc/init.d/radiusd start is OK > > service radiusd start does not work. > > The above two are almost equivalent, if the init script works, as you > indicate in the first line, then the service command should also work > because all it does is call the init script. Check permissions and > symlinks if that's the case. You are doing these with root level > permissions right? (e.g. either sudo or su root). > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html