Edward Z. Yang wrote: > Hey all, > > I'm too tired right now to write up a proper report, but would > the following behavior be something y'all be'd interested in > debugging? > We have tested server to server SASL/GSSAPI with replication on RHEL5, but we have not seen this happen. Do you have more than one replication agreement? Would it be possible for you to provide a stacktrace obtained with thread apply all bt in gdb? > * Outgoing incremental GSSAP-authed MMR replications wedge > indefinitely, in Kerberos code. > * It's impossible to do a full update without disabling all > incoming and outgoing replication agreements, because as > soon as another replication goes and gets stuck, everything > else fails. > > Basically, dirsrv+GSSAPI can get into some sort of wedged > state persistent across restarts that means: > > * You can't restart the server without kill -9'ing it > * You can't do a full update > > And the only way to fix it is to reinitialize all replication > agreements. > > Edward > -- > 389 users mailing list > 389-users@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/389-users > -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
