Peter Nixon <listuser@peternixon.net> wrote:
I am consistently finding that if you create more than one IP Pool bigger than a class B network that FreeRADIUS fails to start with an error saying that it cannot fork. It can however be run in debug mode with this config.
Maybe the modules should be initialized *after* forking, not before.
Also, one customer who had only a single class B IP Pool with about 10,000 clients connecting and disconnecting on a regular basis (Around 300 Auth requests and associated Accounting packets per minute between 8am and midnight) is seeing their FreeRADIUS grow over the course of a couple of days until the Linux OOM killer kills it.
Maybe the DB library has a memory leak? In the short term, I would suggest HUP'ing their server every day or so, even if the config hasn't changed. That should tear down the modules & restart them, which might help. Alan DeKok.