To add a little more detailed information to my last post. The remaining
INFO messages I get in my radius.log file happen 1 per auth. My log file
essentially looks like (just a lot bigger):
DATE: Auth: Login OK: [username] (from nas nasname.foo.bar port 51)
DATE: Info: Accounting: login: entry for NAS nasname.foo.bar port 51 duplicate
DATE: Auth: Login OK: [username2] (from nas nasname.foo.bar port 52)
DATE: Info: Accounting: login: entry for NAS nasname.foo.bar port 52 duplicate
Just for more detail. I'm sure this one can be located, seems odd it's
happening 1 for 1 login OK's.
---------- copy of previous message ----------------
Excellent release. I do notice one item we discussed earlier when I was
running 0.1 regarding the tons of duplicate Accounting requests while proxying.
sample line:
DATE: Info: Accounting: login: entry for NAS nasname.foo.bar port 51 duplicate
The patch Chris Parker posted does a good job eliminating most of the
duplicate Info logs requests in radius.log, but it is not implemented in 0.2.
----------- BEGIN PATCH -----------------
the 'acct.c' file:
Change:
if(pairfind(request->config_items, PW_PROXY_TO_REALM)) {
To:
if((!request->proxy) && pairfind(request->config_items, PW_PROXY_TO_REALM)) {
----------- END PATCH -----------------
This seems to get rid of about 90% of the erroneous Info: log entries while
still leaving all proxy accounting data in-tact. I do still get a few
duplicate's in my logs though and am curious why they are still showing up.
A useful addition to freeradius would be the option of using separate log
files. Since we use the radius.log file and parse the data out of it every
month for proxy radius customers, it would be a lot cleaner if we could log
Info: requests to say, perhaps a user defineable file like
info-radius.log. Perhaps one for Warning:'s too.
----------------------------------
Nathan Miller
Visp Systems Administration
Voice: 541-476-5352 ext. 4
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
