[389-users] Re: Restore from Backup Fails

On 1/9/20 5:13 PM, Elena Rico wrote:
>> Remove "-n userRoot" from the restore script, this "false option" was
> Removing this option from 'bak2db' fixed issue 1) however, 'bak2db.pl' still causes ns-slapd to crash.


Did you remove "-n userRoot" from the perl script?  What was the exact
CLI command you used?  Can you provide the same script output like you
did last time?

If the server is crashing we need to fix that.  Can you get a stack
trace from the crash?

https://www.port389.org/docs/389ds/FAQ/faq.html#debugging-crashes

If its reproducible on demand maybe you could attach gdb and get a live
stack trace of the crash.  First follow the prerequisites from the link
above (install debuginfo packages, etc).  Then find the slapd process
id, attach gdb, reproduce crash, and get the stack trace:

# ps -ef | grep slapd

# gdb -p PID_OF_SLAPD_PROCESS

- enter "c" to continue at gdb prompt:   (gdb) c  <press enter>

--> run bak2db.pl

--> process should crash in gdb

(gdb) thread apply all bt full


Send us the entire output.

Thanks,

Mark



>
>
>> Was the backup from a different
>> instance/server?
>>
>> Looks like it's a bad backup but hard to say.  You could run dbverify on
>> your backup directory to see if it complains about anything:
> The backup was made from the same server, running 'dbverify' didn't find any issues in the backup.
>
>
>> This launches a task to perform the backup but the script returns before
>> the task is even started, then below you are doing db2ldif's.  Potential
>> race condition.   I'm not sure if that could be causing an issue, but
>> the db2ldif should be done after the backup (db2bak) is complete.
>> Ideally this should all be done while the server is stopped, but it's
>> not a requirement.
> We will look into this changes in more detail to make see if this is causing the issues.
>
> Thanks Mark for the prompt reply, it has helped us a lot to better understand the backup and restore scripts.
>
> Elena
>
> _______________________________________________
> 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

--

389 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