On 12/10/18 2:55 PM, KONG, BOB wrote:
I have a simple question I hope…
We currently have a master 389 Directory Server on 1.2.11 and I was
wondering if it is possible to replicate to a 389 Directory Server
1.3.8 consumer? Has anyone done this?
Yes this should work just fine
Thanks in
Resolved.
I’ve upgrade Java and now the client works. Not sure why the version of java
nor 389 client was working for so long before it broke. Thanks all for your
help.
From: Jason Jenkins
Date: Thursday, December 6, 2018 at 11:50 AM
To: Viktor Ashirov , "389-users@lists.fedoraproject.org"
Hi there, we have four IPA servers 4.4.0 and 389-ds is 1.3.5.10-11, and there
is multi master replication among some of them.
There is daily backup via ipa-backup, and on one server it failed because of
disk space. The /var/log/dirsrv/slapd-EXAMPLE-COM/errors read:
- NSMMReplicationPlugin -
Restore is one way t proceed.
A quick way to recover the LDAP service in this situation, is to remove the
changelog files and let 389-ds create new ones at start up.
Then check for consistency as much as possible.
Eventually re-init from another replica.
The recovery process may take "some time",
Thanks Marc, and what files / directories exactly to remove?
[1] I see many db file in /var/lib/dirsrv/slapd-US-COM/db/changelog/ directory
aci.db
ancestorid.db
changenumber.db
cn.db
DBVERSION
entryrdn.db
entryusn.db
id2entry.db
nsuniqueid.db
numsubordinates.db
objectclass.db
parentid.db
I was able to restore 389ds data and start service after below exercises.
[ on failed-server] ipa-restore -d --data
/var/lib/ipa/backup/ipa-data--mm-dd-hh-mm-ss
[ on failed-server] systemctl start dirsrv@US--COM.service
[ on failed-server] ipa-replica-manage -v re-initialize
