Thanks for your answer. I did as you told ( /usr/sbin/radiusd -f -xx -lstdout), but as I said, when I start freeradius manually, it works well, so I don't have any error in the logs. My problem is to have the same kind of logs when launching Freeradius with the service call (service radiusd start). If I do that, I don't have any logs to see why the script call isen't executed... 2015-04-16 13:32 GMT+02:00 Arran Cudbard-Bell <a.cudbardb@freeradius.org>:
It looks that in both case is the same user (radiusd) that runs the shell script, but it only works when manually starting Freeradius. Maybe it's a timing issue?
no.
Is there a way to see any logs when running *service radiusd start *? My /var/log/raddb/radius.log don't show any detailed information (neither /var/log/radius/radacct/<client IP>/auth-detail-20150415)...
sudo /usr/sbin/radiusd -f -xx -lstdout
That'll give you debug output, with the radius process running with its euid/egid running as the ones set in radiusd.conf.
-Arran
Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html