[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Error in 2.0.25 ?
Hi,
I am suggesting that there was a packet that may have not had the expected
number of bytes to complete the transaction successfully. In terms of secure
transactions (i.e. MD5) it would complain about dropped packets as it may be
assumed that this may have encountered a hack (but that is not necessarly
true, could be collisions, faulty net card and so on).
-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Harry Ruter
Sent: Tuesday, June 11, 2002 5:07 PM
To: OpenLDAP-software@OpenLDAP.org
Subject: Re: Error in 2.0.25 ?
Hi,
Dhiren Pankhania wrote:
>
> Does that not mean the packet length recieved is not correct ? Basically
an
> intergrity check or CRC check done by SASL.
Don't know what it means,
but it must belong to the replication-process,
as changing of data works fine on the server
(but not on the replica-server).
greets Harry
> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Harry Ruter
> Sent: Tuesday, June 11, 2002 4:40 PM
> To: OpenLDAP-software@OpenLDAP.org
> Subject: Error in 2.0.25 ?
>
> Hi,
>
> is there anaother error in 2.0.25.
> What i do :
>
> I've configured a server/replica-server-environment.
> Changing data (of type displayname) gives the following in
> logfiles :
>
> ---------------------snipp----------------------
> do_sasl_bind: dn (uid=ldapreplicator+realm=HRNET.DE) mech
> GSSAPI
> SASL Authorize [conn=15]: "ldapreplicator" as
> "u:ldapreplicator"
> slap_sasl_bind: username="u:ldapreplicator" realm="HRNET.DE"
> ssf=56
> <== slap_sasl_bind: authzdn: "uid=ldapreplicator +
> realm=HRNET.DE"
> send_ldap_sasl: err=0 len=-1
> send_ldap_response: msgid=4 tag=97 err=0
> ber_flush: 14 bytes to sd 17
> <== slap_sasl_bind: rc=0
> connection_get(17): got connid=15
> connection_read(17): checking for input on id=15
> ldap_pvt_sasl_install
> ber_get_next
> sb_sasl_pkt_length: received illegal packet length of 987
> bytes
> ber_get_next on fd 17 failed errno=0 (Success)
> connection_read(17): input error=-2 id=15, closing.
> connection_closing: readying conn=15 sd=17 for close
> connection_close: conn=15 sd=17
> TLS trace: SSL3 alert write:warning:close notify
> ---------------------snipp----------------------
>
> The question is:
> What's illegal with a
> "packet length of 987 bytes" ?
>
> greets Harry