Freeradius 3.0.8 Can't create UNIX socket and Too many open files

Rui Ribeiro ruyrybeyro at
Wed Apr 29 10:11:15 CEST 2015

> Message: 6
> Date: Tue, 28 Apr 2015 23:04:26 +0200
> From: Rygl AleŇ° <ales at>
> To: FreeRadius users mailing list
>         <freeradius-users at>
> Subject: Re: Freeradius 3.0.8 Can't create UNIX socket and Too many
>         open files
> Message-ID: <201504282304.26562.ales at>
> Content-Type: Text/Plain;  charset="utf-8"
> Hi Ales,

Are you? Possibilities of dedicating a standalone machine to freeradius,
paravirtualization of disk access in vmware environments, offloading syslog
to other servers, PARTITION or SHARDING, and you have not mentioned
innodb_file_per_table=1 which was made default only in recent versions.

Have also a look at this, (I have
an idea there is a similar, more recent one, cannot find it atm).

Of course, as Alan says, all the best strategies start for not using the DB
for certain situations in the first place.

If using AD for authentication, I would have also a look at the recent
developments of authenticating directly against SAMBA >= 4.2.x


> We have ~1M of records in radacct table and all of them are on-line
> sessions.
> That's the problem. I am cleaning closed sessions every 20s, which removes
> ~2k
> records to the "historical" table. Maybe some partitioning or data split
> could
> help here.
> >   No amount of poking FreeRADIUS will make the database run faster.  Any
> > changes to FreeRADIUS just work around the issue.  They don't fix the
> > issue.
> I guess I am touching the limits of the DB here.
> Regards
> Ales


Rui Ribeiro
Senior Sysadm

More information about the Freeradius-Users mailing list