Radius crashing with "Failed adding event handler for socket: Too many readers"

[Campbell McKenzie]

Hello,

I'm running Free Radius 3.0.16 on Redhat 7 and the about once or 10 times a day the service will "crash" (Exit with error code 1) with the error message "Failed adding event handler for socket: Too many readers".

The only messages prior to Radius crashing are:

Mar 19 21:37:34 radius1.acme.com radiusd[11344]: ... adding new socket proxy address 202.AA.BB.CC port 57158
Mar 19 21:37:34 radius1.acme.com radiusd[11344]: ... adding new socket proxy address 202.AA.BB.CC port 57158
Mar 19 21:37:34 radius1.acme.com radiusd[11344]:Failed adding event handler for socket: Too many readers

Then systemd picks up the failure:

Mar 19 21:37:34 radius1.acme.com systemd:radiusd.service: main process exited, code=exited, status=1/FAILURE
Mar 19 21:37:34 radius1.acme.com systemd:Unit radiusd.service entered failed state.
Mar 19 21:37:34 radius1.acme.com systemd:radiusd.service failed.

Our configuration consists of about 157 home_servers (mostly running in auth+acct) and about 276 clients and two upstream proxies. (Eduroam).

It seems like a new socket is created for each home_server (auth) + another socket for accounting and with such a high(?) number of home_servers we are running out of sockets (possibly).

Is there a limit to the number of home_servers and/or clients?

Kind regards,
Campbell

Campbell McKenzie
AARNet Pty Ltd

address: Tenancy 1, Ground Floor, 143 Coronation Drive, Milton, QLD, 4064, Australia
postal:  PO Box 1787, Milton, Qld, 4064
w. www.aarnet.edu.au