I am wondering if i really use the bug fix for reading detail file...
how can i make sure it's compiled with the bug fix?
Alexandre Chapellon a écrit :
If it helps: while compiling freeradius 2.0.2 for my debian (using
dpkg suite) I had to undefine the CISCO_ACCOUNTING_HACK to avoid
accouting problem with rlm_sql.
I'm not sure its related with my problem but I prefer to say it.
P.S: its compiled for amd64 arch
Alexandre Chapellon a écrit :
Hello all
I come back with the same problem.... I don't want to annoy anybody
but I'm still clueless.
I use the fresh freeradius 2.0.2 as an accounting server (to a mysql
database) but I have other server that must host accounting
informations too (1 billing server and 2 for a content filtering
product).
I have tried to replicate my accouting data using
copy-acct-to-home-server virtualhost:
server copy-acct-to-home-server {
listen {
type = detail
filename = ${radacctdir}/detail
load_factor = 10
}
preacct {
suffix
}
while prior sql accouting is done by another virtual server that
writes too the detail file (with the option locking = yes) used by
copy-acct-to-home-server:
server local_acct {
accounting {
detail_replic
sql
}
}
I have noticed that the detail file never gets read totaly (usually
only one request) and so only few (most of the time one) requests get
effectively proxied to the home server.
I can't understand why... is it something contained in the
request/response...
I'm really clueless and would greatly appreciate any help.
I have an addditionnal question.... will it be possible to copy
accounting to 3 servers, and how?
Thx
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
