I have performed the following actions, however, the listener files are
still being deleted when the home accounting server is down.
# Mark this home server alive ONLY when it starts being responsive
status_check = status-server
You have altered this from robust-proxy-accounting exampl
JDL wrote:
> I have performed the following actions, however, the listener files are
> still being deleted when the home accounting server is down.
Please run it in debugging mode. The output is likely too large to
post here, but only debugging mode will tell you what's happening.
It will pr
I have performed the following actions, however, the listener files are
still being deleted when the home accounting server is down.
Alan DeKok wrote:
1) Don't write to the detail file twice.
I have commented out ALL detail lines from all active configuration
files (including sites-enabled/
Alan DeKok wrote:
On top of that, your configuration clearly logs to the detail file
*twice*. Once when the packet is read from the network, and then again
when it's read from the detail file.
I assume you are referring to this
server acct_detail.imaginenet {
accounting {
JDL wrote:
> I just tried the 2.1.5 pre-release and the issue with the detail file
> listener going crazy seems to have been corrected. Thank you.
That's good.
> However, the issue of the spooled detail files being deleted remains.
> Doing my best to analyze the debug file and some copies of th
Alan DeKok wrote:
Some people have seen the detail file listener go "crazy", and use
lots of CPU. I've managed to reproduce the problem, and have committed
a fix to the "stable" tree.
Please see http://git.freeradius.org/pre/ for tar files && debian
files containing the fix. Or, see http:
6 matches
Mail list logo
