Could be a system without enough available RAM to the ns-slapd process,
eventually hitting a previously fixed issue.
But cannot tell for sure without more details.
Try to review the system messages and the ns-slapd errors log file, not
just the systemd general status output.
Thanks,
M.
On Tue,
Thank you for reply, I believe this is a memory issue related see the last
line, we were been waiting patiently for last hours to recover db but no
progress so far .
One of the link you pointed is no working , unfortunately this is not RHEL7.7
is Scientific Linux can not open the a case.
The "recovering database" may take a few minutes to complete.
Check the errors log file again for any newer messages after the recovery.
For the crash, or if till not starting up, try to get a core file and stack
trace:
https://www.port389.org/docs/389ds/FAQ/faq.html#debugging-crashes
