> No.. you told it to log to stderr. That's what "-lstderr" means. > If you don't say "-lstderr", logging goes to wherever it says in > "radiusd.conf", usually "radius.log" somewhere. > > Unless... if you mean that the "radius.log" is one created by > daemontools... > >> Logging had been working fine for almost 2 years then it stops.. >> Something must have changed but where? > > I'm not sure what you're doing, so I can't say for sure. > > Alan DeKok.
No lstderr tells svc (daemontools) to send its errors to stderr not freeradius and we are not talking about standard errors we are talking about authentication entries being added to radius.log when someone logs in auth entries are to be written via either command line options -yz or the entries in radiusd.conf. Guess I dont have to tell you that though. Anyway I solved the problem of the it not logging. The problem was that radiusd is set to run as user radius and in the config file it was set to user=radius group=radius I removed the existing radius.log file so that a new one would be created but for some reason the new log was created but as root/radius (owner root - group radius) and after radiusd got past the initial startup it starts trying to do things as user radius so when it went to write to the radius.log file that had just been created ( by root) it didnt have permission. I changed the permissions on the radius.log file to radius/radius and all is well now and it is putting in the authentication info like it is supposed to now. Maybe this will help someone in the future. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
