%RADIUS-4-RADIUS_ALIVE | %RADIUS-4-RADIUS_DEAD help

[ramesh p]

And why the process is stopped automaticaly? any reasons.

On Mon, Apr 27, 2009 at 2:05 PM, ramesh p <rock786143 at gmail.com> wrote:

> Thanks. How to configure it?
>
>
> On Mon, Apr 27, 2009 at 1:29 PM, Borislav Dimitrov <
> b.dimitrov at ngsystems.net> wrote:
>
>> Hi there,
>> I may be mistaken but... these are log message on the NAS aren't they?
>> If this is the case, I've experienced similar behavior with Cisco VoIP
>> routers (RADIUS Server DEAD and then... ALIVE). This happens if you haven't
>> properly enabled concurrency in FreeRADIUS - the CPU usage stays low
>> 0%-1%-2% but if the requests are many they are obviously waiting each
>> other... This happens when you have stared FreeRADIUS with the -X key (I
>> think it starts with a single thread then) or have too low values for the
>> thread pool parameters (and/or the *_clones options of rlm_perl which are to
>> be deprecated soon). If you configure proper values according to the
>> expected usage (concurrent requests), then the request won't wait each other
>> to finish while the CPU stays unused and you'll avoid this annoying message
>> in your logs. A sure sing that something like that is going on is the
>> Acct-Delay-Time parameter with values greater than 0 - that is for
>> accounting not sure for auth etc. Anyways if the values of that parameter
>> are high (they are in seconds I think) then the requests are waiting too
>> long and hence the error messages.
>>
>>  On 27.04.2009, at 10:42, Nicolas Goutte wrote:
>>
>>
>>  Am 27.04.2009 um 09:08 schrieb ramesh p:
>>
>>  I'm seeing the following weirdness from my freeradiusserver and when i
>> see the radiusd process its stopped status. why this happens. any valid
>> reasons for this?
>>
>> Apr 26 00:18:44.498: %RADIUS-4-RADIUS_ALIVE: RADIUS server
>> X.X.X.X:0,1813 is being marked alive.
>>
>> Apr 26 00:18:50.777: %RADIUS-4-RADIUS_DEAD: RADIUS server
>> X.X.X.X:0,1813 is not responding.
>>
>> Apr 26 00:18:50.777: %RADIUS-4-RADIUS_ALIVE: RADIUS server
>> X.X.X.X:0,1813 is being marked alive.
>>
>> Apr 26 00:18:59.133: %RADIUS-4-RADIUS_DEAD: RADIUS server
>> X.X.X.X:0,1813 is not responding.
>>
>> Apr 26 00:18:59.133: %RADIUS-4-RADIUS_ALIVE: RADIUS server
>> X.X.X.X:0,1813 is being marked alive.
>>
>> Apr 26 00:19:04.765: %RADIUS-4-RADIUS_DEAD: RADIUS server
>> X.X.X.X:0,1813 is not responding.
>> Thanks in advance.
>>
>>
>>
>> Have you checked the output of radiusd -X if there is a reason given or
>> any other hint?
>>
>>
>> Regards,
>> Rams.
>> -
>> List info/subscribe/unsubscribe? See
>> http://www.freeradius.org/list/users.html
>>
>>
>> Have a nice day!
>>
>>  Nicolas Goutte
>>
>>
>> extragroup GmbH - Karlsruhe
>> Waldstr. 49
>> 76133 Karlsruhe
>> Germany
>>
>> Geschäftsführer: Stephan Mönninghoff, Hans Martin Kern, Tilman Haerdle
>> Registergericht: Amtsgericht Münster / HRB: 5624
>> Steuer Nr.: 337/5903/0421 / UstID: DE 204607841
>>
>>
>>
>> -
>> List info/subscribe/unsubscribe? See
>> http://www.freeradius.org/list/users.html
>>
>>
>>
>> -
>> List info/subscribe/unsubscribe? See
>> http://www.freeradius.org/list/users.html
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20090427/af93ed79/attachment.html>