Initial access requests getting dropped, successive requests succeed

Alan DeKok aland at
Fri Mar 31 20:02:30 CEST 2017

On Mar 31, 2017, at 1:34 PM, Jeremy Stretch via Freeradius-Users <freeradius-users at> wrote:
> Tracing "freeradius -X" yields the following each time a request is dropped:
> select(9, [4 6 7 8], NULL, NULL, NULL)  = 1 (in [6])
> recvfrom(6, 0x7ffe802938d0, 4, 2, 0x7ffe802938e0, 0x7ffe802938cc) = -1
> EAGAIN (Resource temporarily unavailable)
> write(1, "Ready to process requests.\n", 27Ready to process requests.) = 27

  Yup.  It's an OS issue.

> Not sure what to make of that. Seems like it might be related to this bug:
>;msg=2 As far as
> I'm aware though, nothing significant has been changed on these serves.

  There was probably a kernel change.

  Run a kernel that works.  No amount of poking FreeRADIUS will fix the underlying OS.

  Alan DeKok.

More information about the Freeradius-Users mailing list