[389-users] DSA unwilling to process update / Viewing contents of replication updates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I've a cluster of boxes with replication form two multimasters to 6 read only replicas. There appears to be a problem in the replication in that the error logs state that the DSA is unwilling to process updates for a specific user account, so the replication status in the idm just stays at saying it started rather than completed. I could just delete the account and recreate it, but as it's unfortunately *my* account (and is in this state *possibly* because I was messing with the resetpasswordretrytime field (or something very similarly named) which I get the impression is treated differently to other fields) I'd like to avoid deleting the account.

To this end I'm hoping a suitable solution is to remove whatever the change is that is trying to be pushed across, but I can't see any way with SSL replication to see what the actual attributes it doesn't like are. Any way to pull this straight out with ldapsearch or something? Any tips for elegantly troubleshooting this in a heavily locked down environment would be appreciated.

Thanks

Chris
--
389 users mailing list
389-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users

[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux