[389-users] Re: 389ds can't start after "db error (no disk space)" ... space problem has been resolved

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

[389-users] Re: 389ds can't start after "db error (no disk space)" ... space problem has been resolved

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

[389-users] Re: 389ds can't start after "db error (no disk space)" ... space problem has been resolved

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",