[RADIATOR] refresh time on clientlistsql

[Christian Kratzer]

Hi,

On Fri, 8 Oct 2010, Alexander Hartmaier wrote:

> Hi Hugh,
>
> we started to use the ClientListSQL feature too but get an Oracle SQL
> timeout error in the logs whenever Radiator tries to refresh the list,
> works on startup.

just a wild guess but does your oracle timeout idle connections
after a specific time.

We had a similar situation with LDAP sometime ago where were getting
LDAP_OPERATIONS_ERRORs when a connection was reused after a while of
inactivity.

The ldap server had closed the socket after a timeout and radiator
only noticed when it tried to write a query to the socket.

We contributed a fix to AuthbyLDAP2 that reattempts the connect on
errors.  This has since been included in radiator.

What you are describing SQL Connection, Query works first time but
fails a while later sounds awfully similiar.

Just a wild guess though.

Greetings
Christian

>
> Any idea why and how we can debug this?
>
> --
> Best regards, Alex
>
>
> Am Mittwoch, den 22.09.2010, 00:25 +0200 schrieb Hugh Irvine:
>> Hello Alex -
>>
>> See section 5.7.3 in the Radiator 4.7 reference manual ("doc/ref.pdf").
>>
>> regards
>>
>> Hugh
>>
>>
>> On 22 Sep 2010, at 05:01, Martin Burton wrote:
>>
>>> Hi Alex,
>>>
>>> You need to make sure that RefreshPeriod is set in your config file.  It
>>> defaults to 0, which means the SQL query is performed only upon radiusd
>>> start or when it's sent a SIGHUP.
>>>
>>> <ClientListSQL>
>>>     .
>>>     .
>>>     .
>>>     RefreshPeriod 300
>>>     .
>>>     .
>>>     .
>>> </ClientListSQL>
>>>
>>> would cause the the DB to be requeried every 5 minutes for example.
>>>
>>> Hope that helps.
>>>
>>> Cheers,
>>>
>>> Martin.
>>>
>>> On 21/09/2010 19:41, Alex Sharaz wrote:
>>>> Hi all,
>>>>
>>>> I've got a cluster of radius servers all configured to read NAS clients from a db2 database. I thought that radiator was supposed to periodically refresh its internal list of clients by rereading the database.
>>>>
>>>> Yesterday morning I dded a number of clients to the database. by 16:00 today  the radius servers still hadn't picked up the new clients.  A reload caused radiator to reread the client list but it would have been nice to have radiator pic up the new clients automagically.
>>>>
>>>> Anyone else seen problems with refreshing client lists?
>>>>
>>>> Rgds
>>>> Alex
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Checked by  Hu-fw-yhman
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> radiator mailing list
>>>> radiator at open.com.au
>>>> http://www.open.com.au/mailman/listinfo/radiator
>>>
>>> --
>>> Martin Burton
>>> Senior Systems Administrator               \\\|||///
>>> Special Projects Team                     \\  ^ ^  //
>>> Wellcome Trust Sanger Institute            (  6 6  )
>>> -----------------------------------------oOOo-(_)-oOOo---
>>>
>>>
>>> _______________________________________________
>>> radiator mailing list
>>> radiator at open.com.au
>>> http://www.open.com.au/mailman/listinfo/radiator
>>
>>
>>
>> NB:
>>
>> Have you read the reference manual ("doc/ref.html")?
>> Have you searched the mailing list archive (www.open.com.au/archives/radiator)?
>> Have you had a quick look on Google (www.google.com)?
>> Have you included a copy of your configuration file (no secrets),
>> together with a trace 4 debug showing what is happening?
>>
>
>
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
> T-Systems Austria GesmbH   Rennweg 97-99, 1030 Wien
> Handelsgericht Wien, FN 79340b
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
> Notice: This e-mail contains information that is confidential and may be privileged.
> If you are not the intended recipient, please notify the sender and then
> delete this e-mail immediately.
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
>

-- 
Christian Kratzer                      CK Software GmbH
Email:   ck at cksoft.de                  Schwarzwaldstr. 31
Phone:   +49 7452 889 135              D-71131 Jettingen
Fax:     +49 7452 889 136              HRB 245288, Amtsgericht Stuttgart
Web:     http://www.cksoft.de/         Geschaeftsfuehrer: Christian Kratzer