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, Oct 15, 2019 at 11:39 AM I M <isabella.ghiu...@nrc-cnrc.gc.ca> wrote: > 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. > > Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; disabled; vendor > preset: disabled) > Active: failed (Result: signal) since Tue 2019-10-15 10:51:19 PDT; > 40min ago > Process: 12904 ExecStart=/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-%i -i > /var/run/dirsrv/slapd-%i.pid (code=killed, signal=BUS) > Process: 12898 ExecStartPre=/usr/sbin/ds_systemd_ask_password_acl > /etc/dirsrv/slapd-%i/dse.ldif (code=exited, status=0/SUCCESS) > Main PID: 12904 (code=killed, signal=BUS) > _______________________________________________ > 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://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-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://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
