Norman Elton wrote:
> Oh, definitely. We'd do that as a failsafe anyway. My main question is
> whether this is failing by design?
The intention is to *not* crash.
But... FreeRADIUS is dependent on the libraries it uses. If they
misbehave, then there's little we can do.
> If so, is there a b
On Friday, September 2, 2011, Alan Buxey wrote:
> I meant that if you use eg monit then you can have a service recovery
rather than a corner case killing off your radius daemon in middle of night
>
Oh, definitely. We'd do that as a failsafe anyway. My main question is
whether this is failing by d
> Use a wrapper around the demon, eg 'monit' ?
Around the radiusd daemon? Nope. Running it from bash, or in this
case, from within gdb.
Norman
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I've used GDB to generate a stack trace, specifically using the
instructions on http://freeradius.org/radiusd/doc/bugs.
For this particular test case, I configured as I described above, but
instead of a stripped-down example.pl, I just the one provided, but
put "my $i = 1/0;" in the "test_call" su
>> 2.1.11 is out...and 2.1.12 is almost ready for release - does your system
>> behave in the same way with 2.1.11?
>> Are you using a pre-built package for freeradius or one that you have
>> built yourself?
I am using RedHat's pre-built packages, both FreeRADIUS and Perl. I
have not tried newer
On Fri, Sep 02, 2011 at 07:16:26PM +0200, Bjørn Mork wrote:
> Alan Buxey writes:
>
> >> Oh, I've experienced lots of them! So many, in fact, that I figured it
> >> was a common and well understood occurrence. Let me come up with an
> >> easily reproducible example and I'll post the relevant infor
Alan Buxey writes:
>> Oh, I've experienced lots of them! So many, in fact, that I figured it
>> was a common and well understood occurrence. Let me come up with an
>> easily reproducible example and I'll post the relevant information.
>
> 2.1.11 is out...and 2.1.12 is almost ready for release - d
Hi,
> Oh, I've experienced lots of them! So many, in fact, that I figured it
> was a common and well understood occurrence. Let me come up with an
> easily reproducible example and I'll post the relevant information.
2.1.11 is out...and 2.1.12 is almost ready for release - does your system
behave
> Of course a script error shouldn't segfault the server. It would have been
> much more useful if you had explained what the script error was and a stack
> trace from the segfault.
Oh, I've experienced lots of them! So many, in fact, that I figured it
was a common and well understood occurrence.
On 09/02/2011 09:43 AM, Norman Elton wrote:
I'm beginning the process of replacing a home-grown RADIUS server with
freeradius, a good idea on many many fronts. The server will interact
with our backend databases in order to determine attributes to inject
into the access-accept messages. For initi
10 matches
Mail list logo