[389-users] Re: Unable to promote a replica

Looks like there might be some patch missing on the 1.4.4 branch because
dsconf should not be trying to create the changelog.  Can you provide
this info:

# rpm -qa | grep 389

Most likely this is a bug, but for now you can use ldapmodify (from our
older docs):

https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/managing_replication-making_a_replica_updatable

--> you can skip the changelog part

HTH,

Mark

On 8/2/21 7:19 PM, John Thurston wrote:
> I've installed 389-Directory 1.4 on CentOS 8 from EPEL
>   https://directory.fedoraproject.org/docs/389ds/download.html
> it looks like I have 1.4.4
>
> Today's problem is I'm unable to promote a replica from a 'consumer'
> to a 'supplier'. I've tried using the cockpit web-gui, as well as
> dsconf from the command line.
>
> When using cockpit, I get a error box containing:
>
>> Failed to promote replica - Failed to create changelog: {'msgtype':
>> 105, 'msgid': 9, 'result': 53, 'desc': 'Server is unwilling to
>> perform', 'ctrls': [], 'info': 'Changelog configuration is part of
>> the backend configuration'}
>
> when using dnsconf, it returns (essentially) the same thing:
>
>> Error: Failed to create changelog: {'msgtype': 105, 'msgid': 9,
>> 'result': 53, 'desc': 'Server is unwilling to perform', 'ctrls': [],
>> 'info': 'Changelog configuration is part of the backend configuration'}
>
> When I look in the audit-log, I see:
>> time: 20210802150607
>> dn: cn=changelog5,cn=config
>> result: 53
>> changetype: add
>> objectClass: top
>> objectClass: nsChangelogConfig
>> cn: changelog5
>> nsslapd-changelogdir: /var/lib/dirsrv/slapd-dirmaster/changelogdb
>> creatorsName: cn=Directory Manager
>> modifiersName: cn=Directory Manager
>> createTimestamp: 20210802230607Z
>> modifyTimestamp: 20210802230607Z
>
> When I look in the error-log, I see NSMMReplicationPlugin is throwing
> a NOTICE error message:
>
>> NOTICE - NSMMReplicationPlugin - changelog program -
>> changelog5_config_add - Separate changelog no longer supported; use
>> cn=changelog,<backend> instead
>
>
> I interpret these to mean dsconf is trying to define the the attribute
> "nsslapd-changelogdir" on cn=changelog5,cn=config. And that the
> replication plugin is saying, "Not so fast there, cowboy. That's not
> the way it is done any more."
>
>
> What is the correct process to promote a replica?
>
>
--
Directory Server Development Team
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure