aland at deployingradius.com
Sun Aug 16 09:12:41 CEST 2009
Gabriel Blanchard wrote:
> Something was committed recently that's causing it to seg fault.
When? What else is happening with the old request?
> Aug 15 21:41:42 rad03 radiusd: Received conflicting packet from
> client ERXes port 50000 - ID: 98 due to unfinished request 390. Giving
> up on old request.
> Aug 15 21:41:42 rad03 radiusd: ASSERT FAILED event.c:
> request->ev != NULL
> Aug 15 21:41:42 rad03 kernel: pid 62455 (radiusd), uid 133: exited on
> signal 6
> I'll have to dig up a bit deeper to find the cause, but this definitely
> doesn't happen with a stable snapshot from a few days ago.
Maybe the network situation has changed, too.
That assert could be changed to a debug warning. The code removes the
"old" request from the internal tracking table, but only under certain
conditions. If those conditions aren't met, it hits the assert.
e.g. The packet was proxied, etc.
Or, maybe there's a race condition.
More information about the Freeradius-Devel