[389-users] Re: 389 fails to start, libdb: BDB1546 unable to join the environment
> On 5 Feb 2019, at 09:00, Zarko D wrote: > > 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 > update later." > As per this doc: > https://directory.fedoraproject.org/docs/389ds/FAQ/replication-update-status.html > .. this is considered temporary, I am afraid it's permanent in my case. > > For now my work around is having cronjob that repeats "ipa-replica-manage -v > re-initialize --from= " and this gets updates. > This doesn’t exactly sound like a sustainable situation … I believe you can enable verbose rreplication logging by setting the nsslapd-errorlog-level to 8192 which could give us more insight. — Sincerely, William Brown Software Engineer, 389 Directory Server SUSE Labs ___ 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: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
[389-users] Re: 389 fails to start, libdb: BDB1546 unable to join the environment
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 update later." As per this doc: https://directory.fedoraproject.org/docs/389ds/FAQ/replication-update-status.html .. this is considered temporary, I am afraid it's permanent in my case. For now my work around is having cronjob that repeats "ipa-replica-manage -v re-initialize --from= " and this gets updates. ___ 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: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
[389-users] Re: 389 fails to start, libdb: BDB1546 unable to join the environment
> On 5 Feb 2019, at 04:50, Zarko D wrote:
>
> 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 restore was done, 389ds start failed with messages like:
>
> libdb: BDB2506 file changelog/id2entry.db has LSN 21643/9352420, past end of
> log at 21243/6180
> libdb: BDB2507 Commonly caused by moving a database from one database
> environment
> libdb: BDB2508 to another without clearing the database LSNs, or by removing
> all of
> libdb: BDB2509 the log files from a database environment
> dbp->open("changelog/id2entry.db") failed: Invalid argument (22)
>
> And after just removing a file changelog/id2entry.db, I was able to quickly
> start 389ds.
>
If you remove the changelog id2entry, you’ll need to re-init from another
master (if it’s standalone, probably no issue).
> ___
> 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: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
—
Sincerely,
William Brown
Software Engineer, 389 Directory Server
SUSE Labs
___
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: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
[389-users] Re: 389 fails to start, libdb: BDB1546 unable to join the environment
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 restore was done, 389ds start failed with messages like:
libdb: BDB2506 file changelog/id2entry.db has LSN 21643/9352420, past end of
log at 21243/6180
libdb: BDB2507 Commonly caused by moving a database from one database
environment
libdb: BDB2508 to another without clearing the database LSNs, or by removing
all of
libdb: BDB2509 the log files from a database environment
dbp->open("changelog/id2entry.db") failed: Invalid argument (22)
And after just removing a file changelog/id2entry.db, I was able to quickly
start 389ds.
___
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: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
