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
https://www.port389.org/docs/389ds/FAaQ/faq.html#debug-startup-crashes
https://www.port389.org/docs/389ds/FAQ/faq.html#debugging-crashes
https://www.port389.org/docs/389ds/FAaQ/faq.html#debug-startup-crashes
Extra note: the current version is with RHEL-7.7 / 389-ds-base-1.3.9.1-10.el7.x86_64
( includes many fixes since 389-ds-base-1.3.7.5-24.el7_5 )
Thanks,
M.
On Tue, Oct 15, 2019 at 10:21 AM <isabella.ghiurea@xxxxxxxxxxxxxx> wrote:
HI All
one of our multmaster DS crashed over the weekend and will not restart , ther are no errors reported in DS errorlog here are details:
OS:
Linux .el7.x86_64 #1 SMP Tue Jun 26 16:32:21 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
389-DS
389-ds-base-1.3.7.5-24.el7_5.x86_64
and
systemctl status dirsrv@pldapX.service
● dirsrv@pldapX.service - 389 Directory Server pldapX
Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; disabled; vendor preset: disabled)
Active: failed (Result: signal) since Tue 2019-10-15 09:51:26 PDT; 3min 10s ago
Process: 7193 ExecStart=/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-%i -i /var/run/dirsrv/slapd-%i.pid (code=killed, signal=BUS)
Process: 7187 ExecStartPre=/usr/sbin/ds_systemd_ask_password_acl /etc/dirsrv/slapd-%i/dse.ldif (code=exited, status=0/SUCCESS)
Main PID: 7193 (code=killed, signal=BUS)
and last lines from errorlog :
[15/Oct/2019:10:17:29.710924472 -0700] - INFO - Security Initialization - SSL info: TLS_AES_256_GCM_SHA384: enabled
[15/Oct/2019:10:17:29.719454362 -0700] - WARN - Security Initialization - SSL alert: nsTLS1 is on, but the version range is lower than "TLS1.0"; Configuring the version range as default min: TLS1.0, max: TLS1.2.
[15/Oct/2019:10:17:29.719840129 -0700] - INFO - Security Initialization - slapd_ssl_init2 - Configured SSL version range: min: TLS1.0, max: TLS1.2
[15/Oct/2019:10:17:29.721517717 -0700] - INFO - main - 389-Directory/1.3.7.5 B2018.178.1311 starting up
[15/Oct/2019:10:17:34.230509014 -0700] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000
[15/Oct/2019:10:17:34.332786785 -0700] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000
[15/Oct/2019:10:17:34.349651890 -0700] - NOTICE - ldbm_back_start - found 16262020k physical memory
[15/Oct/2019:10:17:34.350079009 -0700] - NOTICE - ldbm_back_start - found 15225948k available
[15/Oct/2019:10:17:34.350389153 -0700] - NOTICE - ldbm_back_start - total cache size: 10523508736 B;
[15/Oct/2019:10:17:34.351750381 -0700] - NOTICE - dblayer_start - Detected Disorderly Shutdown last time Directory Server was running, recovering database.
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
