--Apple-Mail-4--815209214 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
This may sound like a strange question, but couldn't seem to find the answer in the docs:
Would the global "idletimeout" parameter interfere with 'refreshAndPersist' operations in any way?
I ask because I have had yet another instance where my three production consumers did not get a series of updates that it should have. This was hours after successfully adding an accesslog database to all Provider servers in question.
When querying the log database:
ldapsearch -b cn=log -xD uid=log,cn=log -w logpassword -s sub -H ldap://ldap-provider-in-question
I see that the records-in-question were in fact updated as they should have .... but there's absolutely no information hinting towards WHY a remote server would fail to get updates (especially when all LDAP traffic in between the said-hosts is unrestricted and unmoderated). Hence why I began to scrutinize the 'idletimeout' parameter (previously set to 45 seconds, now has been removed entirely from all Providers AND Consumers alike).
Still looking at, testing and contemplating this whole situation ... I'll keep you posted, but am curious if anyone has any input to my question above, thanks.
Jeff
On Oct 1, 2009, at 11:39 PM, Howard Chu wrote:
j@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 logging purposes. It is just that using it for multimaster delta- syncrepl is not yet supported.
-- -- 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=us-ascii
<html><head></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; = "><div>This may sound like a strange question, but couldn't seem to find = the answer in the docs:</div><div><br></div><div>Would the global = "idletimeout" parameter interfere with 'refreshAndPersist' operations in = any way?</div><div><br></div><div>I ask because I have had yet another = instance where my three production consumers did not get a series of = updates that it should have. This was hours after successfully = adding an accesslog database to all Provider servers in = question.</div><div><br></div><div>When querying the log = database:</div><div><br></div><div style=3D"font-size: 14px; = ">ldapsearch -b cn=3Dlog -xD uid=3Dlog,cn=3Dlog -w logpassword -s sub -H = <a = href=3D"ldap://ldap-provider-in-question">ldap://ldap-provider-in-question= </a></div><div><br></div><div>I see that the records-in-question were in = fact updated as they should have .... but there's absolutely no = information hinting towards WHY a remote server would fail to get = updates (especially when all LDAP traffic in between the said-hosts is = unrestricted and unmoderated). Hence why I began to scrutinize the = 'idletimeout' parameter (previously set to 45 seconds, now has been = removed entirely from all Providers AND Consumers = alike).</div><div><br></div><div>Still looking at, testing and = contemplating this whole situation ... I'll keep you posted, but am = curious if anyone has any input to my question above, = thanks.</div><div><br></div><div>Jeff</div><div><br></div><div><br></div><= div><br></div><br><div><div>On Oct 1, 2009, at 11:39 PM, Howard Chu = wrote:</div><br class=3D"Apple-interchange-newline"><blockquote = type=3D"cite"><div><a href=3D"mailto:j@telepaths.org">j@telepaths.org</a> = wrote:<br><blockquote type=3D"cite">Sorry about that .... = resending to ITS address:<br></blockquote><blockquote = type=3D"cite"><br></blockquote><blockquote type=3D"cite">Regarding use = of the accesslog DB ..... is this still an option = when<br></blockquote><blockquote type=3D"cite">using 'mirrormode' ? = I understand at least in the recent past, = this<br></blockquote><blockquote type=3D"cite">option was not compatible = with the accesslog overlay .....<br></blockquote><br>That's not correct. = The accesslog overlay can always be used for logging purposes. It is = just that using it for multimaster delta-syncrepl is not yet = supported.<br><br>-- <br> -- Howard Chu<br> CTO, Symas Corp. = <a = href=3D"http://www.symas.com%22%3Ehttp://www.symas.com</a><br> = Director, Highland Sun <a = href=3D"http://highlandsun.com/hyc/%22%3Ehttp://highlandsun.com/hyc/</a><br> = Chief Architect, OpenLDAP <a = href=3D"http://www.openldap.org/project/%22%3Ehttp://www.openldap.org/project/= </a><br></div></blockquote></div><br></body></html>=
--Apple-Mail-4--815209214--
-
j＠telepaths.org