On 10/2/18 10:47 PM, DaV wrote:
Hi guys,
I am facing an issue of can't start dirsrv-admin service after reboot 389ds server.
Can anyone help me? Thank in advance.
It seems that some files missing after 389ds server reboot.

OS:
CentOS Linux release 7.5.1804 (Core)

Packages:
389-ds-base-1.3.7.5-24.el7_5.x86_64
389-admin-console-doc-1.1.12-1.el7.noarch
389-adminutil-1.1.21-2.el7.x86_64
389-ds-base-libs-1.3.7.5-24.el7_5.x86_64
389-admin-1.1.46-1.el7.x86_64
389-admin-console-1.1.12-1.el7.noarch
389-ds-console-doc-1.2.16-1.el7.noarch
389-ds-1.2.2-6.el7.noarch
389-console-1.1.18-1.el7.noarch
389-ds-console-1.2.16-1.el7.noarch
389-dsgw-1.1.11-5.el7.x86_64

/var/log/dirsrv/admin-serv/error
[Mon Oct 01 04:41:14.628926 2018] [mpm_worker:notice] [pid 1515:tid 139888393697408] AH00295: caught SIGTERM, shutting down [Mon Oct 01 20:15:10.124133 2018] [:warn] [pid 1498:tid 140057745549440] NSSSessionCacheTimeout is deprecated. Ignoring. [Tue Oct 02 00:12:12.064065 2018] [:warn] [pid 1506:tid 140717522962560] NSSSessionCacheTimeout is deprecated. Ignoring. [Tue Oct 02 01:24:15.688367 2018] [:warn] [pid 1486:tid 140470383057024] NSSSessionCacheTimeout is deprecated. Ignoring. [Tue Oct 02 01:24:15.764891 2018] [:notice] [pid 1486:tid 140470383057024] Access Host filter is: *.seczone.com [Tue Oct 02 01:24:15.764904 2018] [:notice] [pid 1486:tid 140470383057024] Access Address filter is: * [Tue Oct 02 01:24:15.789117 2018] [:warn] [pid 1487:tid 140470383057024] NSSSessionCacheTimeout is deprecated. Ignoring. [Tue Oct 02 01:24:15.789651 2018] [mpm_worker:notice] [pid 1487:tid 140470383057024] AH00292: Apache/2.4.6 (CentOS) configured -- resuming normal operations [Tue Oct 02 01:24:15.789670 2018] [core:notice] [pid 1487:tid 140470383057024] AH00094: Command line: '/usr/sbin/httpd -f /etc/dirsrv/admin-serv/httpd.conf' [Tue Oct 02 01:24:15.793251 2018] [:notice] [pid 1489:tid 140470383057024] Access Host filter is: *.seczone.com [Tue Oct 02 01:24:15.793278 2018] [:notice] [pid 1489:tid 140470383057024] Access Address filter is: * [Tue Oct 02 02:05:48.933732 2018] [mpm_worker:notice] [pid 1487:tid 140470383057024] AH00295: caught SIGTERM, shutting down


systemctl status dirsrv-admin -l
● dirsrv-admin.service - 389 Administration Server.
   Loaded: loaded (/usr/lib/systemd/system/dirsrv-admin.service; enabled; vendor preset: disabled)    Active: failed (Result: exit-code) since Wed 2018-10-03 17:34:52 CST; 1h 6min ago   Process: 3290 ExecStart=/usr/sbin/httpd -k start -f /etc/dirsrv/admin-serv/httpd.conf (code=exited, status=1/FAILURE)

Oct 03 17:34:52 vdi-ds-1 systemd[1]: Starting 389 Administration Server.... Oct 03 17:34:52 vdi-ds-1 httpd[3290]: httpd: Could not open configuration file /etc/dirsrv/admin-serv/httpd.conf: No such file or directory


Does this file exist (/etc/dirsrv/admin-serv/httpd.conf) ?

Not sure how this file could disappear, but if it's gone you will need to remove the "389-admin" package and reinstall it.

Regards,

Mark


Oct 03 17:34:52 vdi-ds-1 systemd[1]: dirsrv-admin.service: control process exited, code=exited status=1 Oct 03 17:34:52 vdi-ds-1 systemd[1]: Failed to start 389 Administration Server.. Oct 03 17:34:52 vdi-ds-1 systemd[1]: Unit dirsrv-admin.service entered failed state.
Oct 03 17:34:52 vdi-ds-1 systemd[1]: dirsrv-admin.service failed.

Sincerely,
--
DaV




_______________________________________________
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 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

Reply via email to