Thx for yout return,
Therefore i forgot to say that we use freeradius only in proxy radius mode.
--
View this message in context:
http://freeradius.1045715.n5.nabble.com/FreeRADIUS-exiting-with-Signal-11-on-FreeBSD-tp3293576p5518921.html
Sent from the FreeRadius - User mailing list archive at
ben_iss wrote:
> This problem could be directly causes by network slow moment ?
It's because the RADIUS server is receiving more requests than it can
handle.
This is usually because the database is too slow.
The solution is to fix it so that the database is not slow.
Alan DeKok.
-
List
I use FreeBSD 8.0 with Freeradius 2.1.12 version.
sorry if i don't understand your sentence :
Ugh. Something is free'ing the request when it's still queued. This
*only* can happen when the request is in the queue for more than 30s.
This problem could be directly causes by network slow mome
ben_iss wrote:
> We same problem :
> (radiusd), uid 133: exited on signal 11
On which version?
> Alan say that, this probeme occured, when request still in queue for more
> than 30s.
Where do I say that?
> Do you know if is possible to increase this time or drop requests when
> exceed 30se
Hi all ,
We same problem :
(radiusd), uid 133: exited on signal 11
Alan say that, this probeme occured, when request still in queue for more
than 30s.
Do you know if is possible to increase this time or drop requests when
exceed 30sec ?
Regards,
Ben
--
View this message in context:
h
It started for me at FreeBSD 7.2 and has continued through 8.1 for both
Freeradius 2 from the ports collection and from the official tar file source
distribution. My server is lightly loaded and not really a production system so
I've not run it under gdb. I use the standard kernel scheduler. The
Hugh Blandford wrote:
>
> I have been running a network monitoring program on my server, that
> tracks cpu load, free memory. None of these have moved out of spec.
>
> Load average on the machine hit a high of 0.012.
This is similar to what I've monitored.
> Daniel, one of your emails sug
Hi Alan, Daniel and all,
On 21/12/2010 19:46, Alan DeKok wrote:
Danial wrote:
Here's the full output from gdb:
..l.
#4 0x0806c852 in rad_assert_fail (file=Could not find the frame base for
"rad_assert_fail".
) at util.c:365
#5 0x0806af44 in request_dequeue (request=0x28542b7c, fun=0xbf9fef8
Danial wrote:
> Here's the full output from gdb:
..l.
> #4 0x0806c852 in rad_assert_fail (file=Could not find the frame base for
> "rad_assert_fail".
> ) at util.c:365
> #5 0x0806af44 in request_dequeue (request=0x28542b7c, fun=0xbf9fef8c) at
> threads.c:412
Ugh. Something is free'ing the req
Here's the full output from gdb:
# gdb radiusd
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "
Danial wrote:
> I did what you suggested and have captured another exit:
>
> # gdb radiusd ...
> Program received signal SIGABRT, Aborted.
> [Switching to Thread 28567ac0 (LWP 100051)]
> 0x2831866b in thr_kill () from /lib/libc.so.7
> (gdb)
>
>
> What do you make of this?
You need to f
Tim Sylvester wrote:
>
> You need to run radiusd in single threaded mode. The server forks a couple
> processes to run the server as a daemon and then exits normally. If you
> looked at the process table (ps -ef), you should see a copy of freeradius
> running on your system.
>
> In gdb, set the
: Sunday, December 19, 2010 4:27 PM
> To: freeradius-users@lists.freeradius.org
> Subject: Re: FreeRADIUS exiting with Signal 11 on FreeBSD
>
>
>
> Alan DeKok-2 wrote:
> >
> > If you can, see doc/bugs. Re-build with debugging symbols, run it
> > under "gdb
Alan DeKok-2 wrote:
>
> If you can, see doc/bugs. Re-build with debugging symbols, run it
> under "gdb", and we should be able to get a backtrace containing the
> exact line which has a problem.
>
Ok.
I've read the doc/bugs file.
Removed the installed freeradius.
Recompiled with debugging
Danial wrote:
> Well, I've now monitored an "Exiting normally" event using ktrace:
That helps.
>655 radiusd RET write 84/0x54
>655 radiusd CALL close(0xa)
>655 radiusd RET close 0
>655 radiusd PSIG SIGSEGV SIG_DFL
Ugh.
> It seems I can semi-reliably replicate this
Alan DeKok-2 wrote:
>
> Uh... packets are not signals. Use "ktrace" to monitor signals sent
> to a process.
>
Well, I've now monitored an "Exiting normally" event using ktrace:
/var/log/radius.log:
Sat Dec 18 02:43:43 2010 : Info: Exiting normally.
/var/log/messages:
Dec 18 02:43:43 radius
Danial wrote:
>> If you can, monitor any signals being sent to the server.
>>
> I've had a tcpdump session running
Uh... packets are not signals. Use "ktrace" to monitor signals sent
to a process.
See http://www.gsp.com/cgi-bin/man.cgi?section=1&topic=ktrace
Alan DeKok.
-
List info/sub
Ok. I've been able to monitor another "Exiting normally" event:
Fri Dec 17 06:38:39 2010 : Info: Exiting normally.
Alan DeKok-2 wrote:
>
> Watch the CPU and memory usage by the server.
>
I've been monitoring the server using Cacti for the last few days.
Memory usage shows plenty of free memo
Hugh Blandford wrote:
> 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:
Watch the CPU and memory usage by the server.
> top is also similarly boring.at the present, I don't know what
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 wh
Scott Lambert wrote:
>
> 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?
>
On the last exit, Des 12, NO entry is written in /var/log/messages. On Des 3
there were, in my case, signal 11 entrie
Scott Lambert wrote:
>
> 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?
>
On the last exit, Des 12, NO entry is written in /var/log/messages. On Des 3
there were, in my case, signal 11 entrie
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
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 fro
24 matches
Mail list logo
