> This doesn’t exactly sound like a sustainable situation …
Yes, beside replica failing, I also can't do any work on this server, add
user/host fails, but at least I have a RO server with all updates.
> rreplication logging by setting the nsslapd-errorlog-level to 8192 which
> could
This
Correct, I've run the command:
ipa-replica-manage -v re-initialize --from=
... it completed successfully. The remaining problem is that this 'fixed'
server doesn't get updates from another master, the error is :
"Error (16) : Incremental update connection error. Backing off, will retry
William, I've tried restoring key3.db, cert8.db and secmod.db but it didn't
help.
Since IPA server is a VM, I was able to try different things on VM's clone, and
fortunately (with the luck) I fixed the problem.
Basically I tried different daily backups that I have, and with one of them,
after
Jan, have you resolve this? My 389ds fails to start now with same messages.
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Thanks for reply William, I believe I restored db with command "ipa-restore -d
--data /path/ipa-data-2018-12-30-20-12-00" but 389ds still fails to start .
Restore final logs are:
[03/Feb/2019:22:49:54.229404539 -0800] import ipaca: Closing files...
[03/Feb/2019:22:50:21.082241726 -0800] All
Hi there, this is 389-ds-base-1.3.5.10-11 (part of ipa-server-4.4.0-12.0.1)
and suddenly daily backup has started to fail with messages:
2019-01-28T04:10:04Z INFO Backing up ipaca in REALM-COM to LDIF
2019-01-28T04:10:04Z INFO Waiting for LDIF to finish
2019-01-28T04:10:05Z DEBUG File
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
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
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 -
