Freeradius as a loadbalancer - logging dropped accounting requests

Alan DeKok aland at deployingradius.com
Mon Jun 26 16:31:46 CEST 2017


On Jun 26, 2017, at 10:23 AM, AleŇ° Rygl <ales at rygl.net> wrote:
> 
> FR is using up to 140% CPU of 48 core system (256GiB RAM, SSD array) I have reniced it and assigned real-time ionice class, the overall CPU of the system is about 20%.

  That's a huge system...

> There is no logging to file, no database in loadbalancer config. It does not even listen for authentication. I can disable all unnecessary modules that could slow it down. There is no attributes rewriting or so. I need just accounting balancing with a really minimalistic config.

  OK.

>>  If you're losing packets at 1000 packets/s, FreeRADIUS is not the cause.
> 
> It must be a misunderstanding. The overall drop rate of LB is about 4,6e-05 and drops are finally solved by a retransmission. I was just wonder if there is a way how to detect/log drops or avoid them by config optimisation.

  There's no real way to do that.

  Alan DeKok.




More information about the Freeradius-Users mailing list