Hi Heikki,
Am 12.04.2011 14:09, schrieb Heikki Vatiainen:
> On 04/11/2011 12:26 PM, Karl Gaissmaier wrote:
>
this is strange as Radiator-4.x has explicit support for reconnecting
to ldap servers after an idle timeout.
>>>
>>> Indeed. The function that has "ldap search for ..." error mess
On 04/11/2011 12:26 PM, Karl Gaissmaier wrote:
>>> this is strange as Radiator-4.x has explicit support for reconnecting
>>> to ldap servers after an idle timeout.
>>
>> Indeed. The function that has "ldap search for ..." error message does
>> LDAP reconnect as the first thing. Reconnect should no
Hello,
thanks for your reply!
Am 06.04.2011 23:44, schrieb Heikki Vatiainen:
> On 04/06/2011 03:39 PM, Christian Kratzer wrote:
>
>>> Wed Apr 6 00:32:34 2011: ERR: ldap search for (|(mail=foo)(uid=bar))
>>> failed with error LDAP_SERVER_DOWN.
>>> Wed Apr 6 00:32:34 2011: ERR: Disconnecting fro
On 04/06/2011 03:39 PM, Christian Kratzer wrote:
>> Wed Apr 6 00:32:34 2011: ERR: ldap search for (|(mail=foo)(uid=bar)) failed
>> with error LDAP_SERVER_DOWN.
>> Wed Apr 6 00:32:34 2011: ERR: Disconnecting from LDAP server (server
>> foo.uni-ulm.de:636).
>> Wed Apr 6 00:32:34 2011: DEBUG: Au
Hi,
On Wed, 6 Apr 2011, Karl Gaissmaier wrote:
> Hi RADIATOR team,
>
> I've got a problem with Version 4.7 and AuthBy LDAP2. The LDAP server
> terminates
> the connection after 10min of client idle as configured in slapd.conf.
>
> Seems that the RADIATOR doesn't recognize this, and the first ACC
Hi RADIATOR team,
I've got a problem with Version 4.7 and AuthBy LDAP2. The LDAP server terminates
the connection after 10min of client idle as configured in slapd.conf.
Seems that the RADIATOR doesn't recognize this, and the first ACCESS-REQUEST
after this termination gets the following error:
