Hello,

what happends when you run with "radiusd -X" - does it all work?

As I said, yes it is working fine.

what does /var/log/radius/radiusd.log show?

When I start radius with "radius -X" the log show nothing, but the last line of the output is "Ready to process requests." and all is working fine. When I start radius with the init.d script server is working also fine and the output of the log is the following: Tue Jul 14 14:05:01 2009 : Info: Loaded virtual server inner-tunnel Tue Jul 14 14:05:01 2009 : Info: Loaded virtual server <default> Tue Jul 14 14:05:01 2009 : Info: Ready to process requests. The problem is, when I enable the sql - accounting by uncomment sql in the accounting section of /usr/local/etc/raddb/sites-enabled/default, the radius does only working fine by starting with "radius -X". When I start the radius in this case (uncomment sql) with the init.d script, the radius is not working. As I saw from "ps aux" - output, one radius process started but "netstat -lnpe" shows no listen port (1812-1814). The logfile shows the following output: Tue Jul 14 14:53:04 2009 : Info: Loaded virtual server inner-tunnel Tue Jul 14 14:53:04 2009 : Info: rlm_sql (sql): Driver rlm_sql_mysql (module rlm_sql_mysql) loaded and linked Tue Jul 14 14:53:04 2009 : Info: rlm_sql (sql): Attempting to connect to radius@localhost:/radius Tue Jul 14 14:53:04 2009 : Info: rlm_sql_mysql: Starting connect to MySQL server for #0 Tue Jul 14 14:53:04 2009 : Info: rlm_sql_mysql: Starting connect to MySQL server for #1 Tue Jul 14 14:53:04 2009 : Info: rlm_sql_mysql: Starting connect to MySQL server for #2 Tue Jul 14 14:53:04 2009 : Info: rlm_sql_mysql: Starting connect to MySQL server for #3 Tue Jul 14 14:53:04 2009 : Info: rlm_sql_mysql: Starting connect to MySQL server for #4 Tue Jul 14 14:53:04 2009 : Info: Loaded virtual server <default> As you can see, the last line "Ready to process requests" is missing.

what is your current SELinux setting? 'getenforce' is the name of the command. if its set to 'enforce' then set it to permissive and try running the init.d script again.

I think prehaps that either a file is owned by root from when you were running it as root and therefore the daemon cannot run properly when started as a lower user - or SELinux is getting in the way

I have no experience with SELinux. I'm using debian and I believe that SELinux support compiled in, but disabled by default. Furthermore I believe that this behaviour has nothing to do with SELinux, but the init.d script is working when sql accounting of radius disabled. Best regards, Bernd