But of course I have to ask, is sump actually running?
Yes, sump is running. I thought about mentoning this right after
hitting the send button. I only wish my problem was that simple.
Anyway, back to my problem at hand. I reviewed the logs and found two
reoccuring entries in the access and error logs. They are listed below.
On Sump:
/var/log/dirsrv/slapd-<instance>/errors
[21/May/2018:11:50:45.730639109 -0500] - ERR -
agmt="cn=meTotierod.<domain-name>" (tierod:389) - clcache_load_buffer
- Can't locate CSN 5af9efa80002000f0000 in the changelog (DB
rc=-30988). If replication stops, the consumer may need to be
reinitialized.
/var/log/dirsrv/slapd-<instance>/access
[22/May/2018:22:40:47.308660133 -0500] conn=4574 op=1 SRCH
base="cn=sump.<domain-name>,cn=masters,cn=ipa,cn=etc,<domain-name>"
scope=2 filter="(ipaConfigString=enabledService)"
attrs="ipaConfigString cn"
I found a reference to the CSN on the mailing list, but came up empty.
_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/freeipa-users@lists.fedorahosted.org/message/FZY46P6NIHCIF5T6H6DF5UHDT4OXS72B/
