Hi,
> 1) Could bad accounting packets cause the radiusd process to EXIT?
> 2) Could bad accounting packets result in hung child processes (as seen
> in the gdb output after the radius log file)?
I'd say yes. we ensure that bad packets dont hit our accounting servers eg
accounting {
> I think you may be 'jumping the gun' a wee bit.
>
> The system currently has over 13,000 active sessions.
>
> There were some odd accounting packets, but the vast majority were valid.
> These could be configuration errors or hack attempts (investigating).
Something broke at 2am. Before that you
day, October 18, 2009 10:56 AM
Subject: Re: over 30 radiusd processes - more information
I've continued to try an investigate the root cause of this, and the last
run behaved slightly differently - the parent process seems to have
terminated, and there are more messages in the radius log.
Ther
Craig Campbell wrote:
> I have attached the radius.log file below, as well as gdb sessions for
> the hung processes showing the results of the gd 'bt' and 'list' commands.
The log is interesting.
> Sat Oct 17 02:01:25 2009 : Error: WARNING: Unresponsive child for
> request 165616, in module sql
> I've continued to try an investigate the root cause of this, and the last
> run behaved slightly differently - the parent process seems to have
> terminated, and there are more messages in the radius log.
>
> There were four (4) hung processes left over.
>
> I have attached the radius.log file be
I've continued to try an investigate the root cause of this, and the last
run behaved slightly differently - the parent process seems to have
terminated, and there are more messages in the radius log.
There were four (4) hung processes left over.
I have attached the radius.log file below, as w
6 matches
Mail list logo
