From j@telepaths.org Fri Oct 2 21:03:38 2009
From: j@telepaths.org
To: openldap-bugs@openldap.org
Subject: Re: (ITS#6320)
Date: Fri, 02 Oct 2009 21:03:37 +0000
Message-ID: <200910022103.n92L3bCi036702@boole.openldap.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0726439323174705810=="
--===============0726439323174705810==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
--Apple-Mail-4--815209214
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=3Dus-ascii;
format=3Dflowed;
delsp=3Dyes
This may sound like a strange question, but couldn't seem to find the =20
answer in the docs:
Would the global "idletimeout" parameter interfere with =20
'refreshAndPersist' operations in any way?
I ask because I have had yet another instance where my three =20
production consumers did not get a series of updates that it should =20
have. This was hours after successfully adding an accesslog database =20
to all Provider servers in question.
When querying the log database:
ldapsearch -b cn=3Dlog -xD uid=3Dlog,cn=3Dlog -w logpassword -s sub -H ldap:/=
/ldap-provider-in-question
I see that the records-in-question were in fact updated as they should =20
have .... but there's absolutely no information hinting towards WHY a =20
remote server would fail to get updates (especially when all LDAP =20
traffic in between the said-hosts is unrestricted and unmoderated). =20
Hence why I began to scrutinize the 'idletimeout' parameter =20
(previously set to 45 seconds, now has been removed entirely from all =20
Providers AND Consumers alike).
Still looking at, testing and contemplating this whole situation ... =20
I'll keep you posted, but am curious if anyone has any input to my =20
question above, thanks.
Jeff
On Oct 1, 2009, at 11:39 PM, Howard Chu wrote:
> j(a)telepaths.org wrote:
>> Sorry about that .... resending to ITS address:
>>
>> Regarding use of the accesslog DB ..... is this still an option when
>> using 'mirrormode' ? I understand at least in the recent past, this
>> option was not compatible with the accesslog overlay .....
>
> That's not correct. The accesslog overlay can always be used for =20
> logging purposes. It is just that using it for multimaster delta-=20
> syncrepl is not yet supported.
>
> --=20
> -- Howard Chu
> CTO, Symas Corp. http://www.symas.com
> Director, Highland Sun http://highlandsun.com/hyc/
> Chief Architect, OpenLDAP http://www.openldap.org/project/
--Apple-Mail-4--815209214
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=3Dus-ascii
This may sound like a strange question, but couldn't seem to find =3D
the answer in the docs:
Would the global =3D
"idletimeout" parameter interfere with 'refreshAndPersist' operations in =3D
any way?
I ask because I have had yet another =3D
instance where my three production consumers did not get a series of =3D
updates that it should have. This was hours after successfully =3D
adding an accesslog database to all Provider servers in =3D
question.
When querying the log =3D
database:
I see that the records-in-question were in =3D
fact updated as they should have .... but there's absolutely no =3D
information hinting towards WHY a remote server would fail to get =3D
updates (especially when all LDAP traffic in between the said-hosts is =3D
unrestricted and unmoderated). Hence why I began to scrutinize the =3D
'idletimeout' parameter (previously set to 45 seconds, now has been =3D
removed entirely from all Providers AND Consumers =3D
alike).
Still looking at, testing and =3D
contemplating this whole situation ... I'll keep you posted, but am =3D
curious if anyone has any input to my question above, =3D
thanks.
Jeff
<=3D
div>
On Oct 1, 2009, at 11:39 PM, Howard Chu =3D
wrote:
j(a)telepaths.org=
=3D
wrote:
Sorry about that .... =3D
resending to ITS address:
Regarding use =3D
of the accesslog DB ..... is this still an option =3D
when
using 'mirrormode' ? =3D
I understand at least in the recent past, =3D
this
option was not compatible =3D
with the accesslog overlay .....
That's not correct. =3D
The accesslog overlay can always be used for logging purposes. It is =3D
just that using it for multimaster delta-syncrepl is not yet =3D
supported.
--
-- Howard Chu
CTO, Symas Corp. =3D
http://www.symas.com =3D
Director, Highland Sun
http://highlandsun.com/hyc/ =3D
Chief Architect, OpenLDAP
http://www.openldap.org/project/=
=3D
=3D
--Apple-Mail-4--815209214--
--===============0726439323174705810==--