Andreas Wetzel wrote:
I installed freeRadius 1.1.6 on a FreeBSD 6.2-RELEASE system from the ports
collection, and am trying to get it to log via syslog. I followed the
instructions from the wiki for configuring radiusd to use syslog, but when
radiusd starts, I get the following:
1.1.6
Jay Banks wrote:
Here is the same problem, found in the archives for this list, which was
posted back in January of 2004:
BUG?? Couldn't open syslog/radius.log for logging: Not a directory
Problem Summary: radiusd: radiusd: Couldn't open syslog/radius.log for
logging: Not a directory
Hi
I installed freeRadius 1.1.6 on a FreeBSD 6.2-RELEASE system from the ports
collection, and am trying to get it to log via syslog. I followed the
instructions from the wiki for configuring radiusd to use syslog, but when
radiusd starts, I get the following:
# radiusd -f -l syslog
Sun Jul 1
# radiusd -f -l syslog
Sun Jul 1 10:40:09 2007 : Info: Starting - reading configuration files
...
radiusd: Couldn't open syslog/radius.log for logging: Permission denied
(rlm_eap_tls: Loading the certificate file as a chain)
radiusd: Couldn't open syslog/radius.log for logging:
Jay Banks wrote:
# radiusd -f -l syslog
Sun Jul 1 10:40:09 2007 : Info: Starting - reading configuration files
...
radiusd: Couldn't open syslog/radius.log for logging: Permission denied
(rlm_eap_tls: Loading the certificate file as a chain)
radiusd: Couldn't open syslog/radius.log for
Both error messages seem to originate from modules during their
initialization
(rlm_eap_tls / rlm_passwd). After a quick look at the source, I would say,
this is due to calling radlog()/vradlog() from the module initialization
or
elsewhere, *before* the 'radlog_dest' variable is correctly
Perhaps this might help -- Jay-=-=-=-=-=Didn't know freeradius did syslog,
cool. Anyway, just tried it out on
freebsd 5.4. In man radiusd, it shows that when using -l syslog, there is
also -g to specify the facility, where it also shows the default is
daemon.
You will need to edit
7 matches
Mail list logo
