Re: (ITS#7178) pcache ttr issues
by mhardin＠symas.com
Fix verified. You can close this one.
Thanks!
-Matt
On Feb 22, 2012, at 1:47 PM, mhardin(a)symas.com wrote:
> Full_Name: Matthew Hardin
> Version: 2.4.29
> OS: Linux (Debian 6, x86_64)
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (170.215.93.127)
>
>
> When proxycache overlay is configured with a time-to-refresh (TTR) value and the
> entry being refreshed is no longer available on the remote server, the refresh
> operation continues sending ldap search requests to the server, to which the
> server responds with an error 2 and a text of "invalid deref".
>
> The following log excerpt is from the remote server:
>
> 4f3f7580 conn=1003 op=55 SRCH base="ou=people,dc=example,dc=com" scope=1 deref=0
> filter="(&(objectClass=posixAccount)(uidNumber=10001))"
> 4f3f7580 conn=1003 op=55 SRCH attr=cn uid uidNumber gidNumber homeDirectory
> userPassword loginShell gecos description objectClass
> 4f3f7580 conn=1003 op=55 SEARCH RESULT tag=101 err=0 nentries=0 text=
> 4f3f7580 conn=1003 op=56 SEARCH RESULT tag=101 err=2 nentries=0 text=invalid
> deref"
>
> The old entry remains in the cache and is returned as the current value.
>
>
11 years, 7 months
Re: (ITS#7179) pcache ttr issues
by mhardin＠symas.com
This is a DUP of 7178 and should be closed.
This was the result of clicking the "compose comment" button found on the ITS display screen. Seems like a malfunction, or at least a non-intuitive result.
-Matt
On Feb 22, 2012, at 4:02 PM, openldap-its(a)OpenLDAP.org wrote:
>
> *** THIS IS AN AUTOMATICALLY GENERATED REPLY ***
>
> Thanks for your report to the OpenLDAP Issue Tracking System. Your
> report has been assigned the tracking number ITS#7179.
>
> One of our support engineers will look at your report in due course.
> Note that this may take some time because our support engineers
> are volunteers. They only work on OpenLDAP when they have spare
> time.
>
> If you need to provide additional information in regards to your
> issue report, you may do so by replying to this message. Note that
> any mail sent to openldap-its(a)openldap.org with (ITS#7179)
> in the subject will automatically be attached to the issue report.
>
> mailto:openldap-its@openldap.org?subject=(ITS#7179)
>
> You may follow the progress of this report by loading the following
> URL in a web browser:
> http://www.OpenLDAP.org/its/index.cgi?findid=7179
>
> Please remember to retain your issue tracking number (ITS#7179)
> on any further messages you send to us regarding this report. If
> you don't then you'll just waste our time and yours because we
> won't be able to properly track the report.
>
> Please note that the Issue Tracking System is not intended to
> be used to seek help in the proper use of OpenLDAP Software.
> Such requests will be closed.
>
> OpenLDAP Software is user supported.
> http://www.OpenLDAP.org/support/
>
> --------------
> Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.
>
11 years, 7 months
(ITS#7179) pcache ttr issues
by mhardin＠symas.com
Full_Name: Matthew Hardin
Version: 2.4.29
OS: Linux (Debian 6, x86_64)
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (170.215.93.127)
When proxycache overlay is configured with a time-to-refresh (TTR) value and the
entry being refreshed is no longer available on the remote server, the refresh
operation continues sending ldap search requests to the server, to which the
server responds with an error 2 and a text of "invalid deref".
The following log excerpt is from the remote server:
4f3f7580 conn=1003 op=55 SRCH base="ou=people,dc=example,dc=com" scope=1 deref=0
filter="(&(objectClass=posixAccount)(uidNumber=10001))"
4f3f7580 conn=1003 op=55 SRCH attr=cn uid uidNumber gidNumber homeDirectory
userPassword loginShell gecos description objectClass
4f3f7580 conn=1003 op=55 SEARCH RESULT tag=101 err=0 nentries=0 text=
4f3f7580 conn=1003 op=56 SEARCH RESULT tag=101 err=2 nentries=0 text=invalid
deref"
The old entry remains in the cache and is returned as the current value.
11 years, 7 months
(ITS#7178) pcache ttr issues
by mhardin＠symas.com
Full_Name: Matthew Hardin
Version: 2.4.29
OS: Linux (Debian 6, x86_64)
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (170.215.93.127)
When proxycache overlay is configured with a time-to-refresh (TTR) value and the
entry being refreshed is no longer available on the remote server, the refresh
operation continues sending ldap search requests to the server, to which the
server responds with an error 2 and a text of "invalid deref".
The following log excerpt is from the remote server:
4f3f7580 conn=1003 op=55 SRCH base="ou=people,dc=example,dc=com" scope=1 deref=0
filter="(&(objectClass=posixAccount)(uidNumber=10001))"
4f3f7580 conn=1003 op=55 SRCH attr=cn uid uidNumber gidNumber homeDirectory
userPassword loginShell gecos description objectClass
4f3f7580 conn=1003 op=55 SEARCH RESULT tag=101 err=0 nentries=0 text=
4f3f7580 conn=1003 op=56 SEARCH RESULT tag=101 err=2 nentries=0 text=invalid
deref"
The old entry remains in the cache and is returned as the current value.
11 years, 7 months
