FreeRADIUS exiting with Signal 11 on FreeBSD

[Hugh Blandford]

Hi Scott,

On 14/12/2010 11:21, Scott Lambert wrote:
> On Sun, Dec 12, 2010 at 02:14:25PM -0800, Danial wrote:
>> I've been having the same problem for quite some time.
>>
>> I'm currently running FreeRADIUS 2.1.10 on i386 FreeBSD 8.1-RELEASE.
>> Accounting packets are written file + two extra detail logs which are
>> proxied.
>>
>> For me I think this "Exiting normally" problem started happening after
>> upgrading FreeBSD from either 7.x to 8 or 6.x to 7.x.
>> It's been happening for over a year now. Sometimes it happens three times a
>> day and sometimes it runs fine for a month.
>> This accounts for the last two months:
>>
>> Tue Oct 12 23:47:18 2010 : Info: Exiting normally.
>> Wed Oct 20 14:16:56 2010 : Info: Exiting normally.
>> Thu Oct 28 09:44:02 2010 : Info: Exiting normally.
>> Mon Nov 29 15:51:27 2010 : Info: Exiting normally.
>> Mon Nov 29 19:47:59 2010 : Info: Exiting normally.
>> Tue Nov 30 08:07:55 2010 : Info: Exiting normally.
>> Wed Dec  1 13:37:36 2010 : Info: Exiting normally.
>> Thu Dec  2 02:25:16 2010 : Info: Exiting normally.
>> Fri Dec  3 02:40:00 2010 : Info: Exiting normally.
>> Fri Dec  3 13:37:48 2010 : Info: Exiting normally.
>> Fri Dec  3 20:04:01 2010 : Info: Exiting normally.
>> Sun Dec 12 07:30:27 2010 : Info: Exiting normally.
>>
>> I don't see any system in the behaviour. It happens at random hours.
>> This is a secondary server, so the number of accounting requests per day
>> varies between 0 and 20000, whereas on a normal day it serves around 100.
>>
>> If nobody has a clue what might cause this behaviour, perhaps somebody is
>> willing to support me/us in debugging this!
> I've not had any issues with FreeRADIUS on FreeBSD 7 since version
> 2.0ish.  Around 2.0 FreeRADIUS ate memory and would be killed when
> the box ran out of swap.  That was a known bug in FreeRADIUS and
> since I upgraded beyond the fix for that, no problems.
>
> What is logged in the 3 or 4 hundred lines before the exits?  Any
> pattern in those messages?  What is logged in /var/log/messages at
> those times?
>
I can see no pattern in my radius.log that is consistent for all of the 
exits.  As this server is fairly quiet /var/log/messages is really quite 
empty:

an example

Dec  4 12:54:26 cata su: test to root on /dev/pts/1
Dec  5 05:14:57 cata kernel: pid 68292 (radiusd), uid 133: exited on 
signal 11
Dec  5 08:39:50 cata su: test to root on /dev/pts/1
Dec  5 08:51:23 cata slapd[93791]: OTP unavailable because can't 
read/write key database /etc/opiekeys: Permission denied
Dec  5 20:47:11 cata kernel: pid 79883 (radiusd), uid 133: exited on 
signal 11

top is also similarly boring.....at the present, I don't know what it 
looks like just after FreeRADIUS exits.  I will investigate it next time 
it happens.

Regards,

Hugh


-- 
Hugh Blandford
Island Internet
ph 1300 130 428
mb 0412 016 875