[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: OL 2.3.19, delta-syncrepl issue



On Fri, 2006-02-03 at 14:34 -0500, Samuel Tran wrote:
> Hi All,
> 
> I am testing delta-syncrepl with two Debian Sarge Linux boxes running OL
> 2.3.19 + 2 patches (ITS #4369 and #4376).

> Feb  3 14:09:51 info-ldap-001 slapd[8424]: => access_allowed: backend
> default read access granted to
> "cn=syncrepl,ou=Accounts,ou=Apps,dc=example,dc=com"
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: => access_allowed: read
> access to "reqStart=20051227213506.000001Z,cn=accesslog" "reqType"
> requested
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: => access_allowed: backend
> default read access granted to
> "cn=syncrepl,ou=Accounts,ou=Apps,dc=example,dc=com"
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: => access_allowed: read
> access to "reqStart=20051227213506.000001Z,cn=accesslog" "reqDN"
> requested
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: => access_allowed: backend
> default read access granted to
> "cn=syncrepl,ou=Accounts,ou=Apps,dc=example,dc=com"
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: => access_allowed: read
> access to "reqStart=20051227213506.000001Z,cn=accesslog" "entryCSN"
> requested
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: => access_allowed: backend
> default read access granted to
> "cn=syncrepl,ou=Accounts,ou=Apps,dc=example,dc=com"
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: ber_flush failed errno=32
> reason="Broken pipe"
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: connection_closing: readying
> conn=43 sd=18 for close
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: send_search_entry: conn 43
> ber write failed.
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: connection_resched:
> attempting closing conn=43 sd=18
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: connection_close: conn=43
> sd=18
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: daemon: removing 18
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: conn=43 fd=18 closed
> (connection lost on write)
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: daemon: activity on 1
> descriptor
> Feb  3 14:09:51 info-ldap-001 slapd[8424]: daemon: activity on:
> Feb  3 14:09:51 info-ldap-001 slapd[8424]:  18r
> Feb  3 14:09:51 info-ldap-001 slapd[8424]:
> 
> I am not sure what that "broken pipe" error means.
> 

On the consumer I have this error message in the logs:

Feb  3 14:37:11 info-ldap-002 slapd[25375]: do_syncrep2: got search
entry without control
Feb  3 14:37:11 info-ldap-002 slapd[25375]: conn=0 op=2 UNBIND
Feb  3 14:37:11 info-ldap-002 slapd[25375]: conn=0 fd=12 closed
Feb  3 14:37:16 info-ldap-002 slapd[25375]: do_syncrep2: got search
entry without control
Feb  3 14:37:51 info-ldap-002 last message repeated 7 times
Feb  3 14:38:56 info-ldap-002 last message repeated 13 times
Feb  3 14:39:01 info-ldap-002 slapd[25375]: do_syncrep2: got search
entry without control
Feb  3 14:39:06 info-ldap-002 slapd[25375]: do_syncrep1:
ldap_sasl_bind_s failed (-1)
Feb  3 14:39:16 info-ldap-002 last message repeated 2 times
Feb  3 14:39:21 info-ldap-002 slapd[25375]: do_syncrep2: got search
entry without control
Feb  3 14:39:56 info-ldap-002 last message repeated 7 times

Thanks.
Sam