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

Re: errant SASL/GSSAPI setup?

--On Wednesday, August 30, 2006 3:44 PM -0400 "Allan E. Johannesen" <aej@WPI.EDU> wrote:

"quanah" == Quanah Gibson-Mount <quanah@stanford.edu> writes:

quanah> The reason things still work between (d) & (e) is because the quanah> connection is *persistent*. The ldap/* bit for the master is only quanah> necessary for establishing the initial connection. That is why quanah> replication continues to work on my ldap slaves even though they don't quanah> have an ldap/* principal in their ticket cache any more:

Ok.  I did a run with -d-1 on master and slave.  This is the relavent
stuff from the LDAP master:

SASL [conn=1] Failure: GSSAPI Error: The context has expired (No error)
sb_sasl_write: failed to encode packet: generic failure
ldap_write: want=11176 error=Input/output error
ber_flush failed errno=5 reason="Input/output error"
connection_closing: readying conn=1 sd=13 for close

Hm, I dunno what to say... My replica's haven't restarted for over 2 days, and syncrepl replication continues w/o issue...


-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html