[389-users] Re: Debugging schema replication errors

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

 




On 2/19/25 4:31 PM, John Thurston via 389-users wrote:

We have a three-server installation; one R/W, replicating to two R/O instances. They are running 389-Directory/2.5.2

On the R/W instance, we are seeing a steady stream of errors of like:

ERR - NSMMReplicationPlugin - agmt="cn=S1" (az1:636): Schema replication update failed: Constraint violation ERR - NSMMReplicationPlugin - agmt="cn=S1" (az1:636): Warning: unable to replicate schema: rc=1

for both replication targets (i.e. both S1 and S2)

I've exported, and examined, the replication change log. I don't see anything in it I don't expect to see. It's full of normal, day-to-day attribute adjustments.

I think the next step is enabling replication logging on a consumer. And I think this is accomplished by adding 8,192 to the value in nsslapd-errorlog-level of cn=config

Yes this is the next step and it should say why the schema replication is not working.

So you can set the error log level using ldapmodify or dsconf. Editing the dse.ldif is not recommended.


# dsconf slapd-YOUR_INSTANCE config replace nsslapd-errorlog-level=8192

Do this on two servers where the error is happening, when you're done reproducing the problem you can turn the verbose logging off using:

# dsconf slapd-YOUR_INSTANCE config replace nsslapd-errorlog-level=0

HTH,

Mark

On our test servers, I've found I can change this value by stopping the instance and editing the dse.ldif  Is there another way to do this which does not require stopping and starting the instance?
--
--
Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston@xxxxxxxxxx
Department of Administration
State of Alaska

--
Identity Management Development Team

--
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux