2:39 p.m.
We have 2 servers in our AWS west environment running CentOS 7. The server just went
unresponsive and I rebooted it. After it came back up it won't start drisrv service.
I get the following errors from systemd/journalctl:
[root@freeipa02 slapd-EXAMPLE-NET]# systemctl status dirsrv(a)EXAMPLE.NET -l●
dirsrv(a)EXAMPLE.NET.service - 389 Directory Server EXAMPLE.NET. Loaded: loaded
(/usr/lib/systemd/system/dirsrv@.service; enabled; vendor preset: disabled) Active:
failed (Result: resources)
Nov 16 20:27:46 freeipa02.west.example systemd[1]: dirsrv(a)EXAMPLE.NET.service failed to
run 'start-pre' task: No such file or directoryNov 16 20:27:46
freeipa02.west.example systemd[1]: Failed to start 389 Directory Server EXAMPLE.NET..Nov
16 20:27:46 freeipa02.west.example systemd[1]: Unit dirsrv(a)EXAMPLE.NET.service entered
failed state.Nov 16 20:27:46 freeipa02.west.example systemd[1]: dirsrv(a)EXAMPLE.NET.service
failed.Nov 16 20:27:46 freeipa02.west.example systemd[1]: Starting 389 Directory Server
EXAMPLE.NET....Nov 16 20:29:10 freeipa02.west.example systemd[1]: Failed to load
environment files: No such file or directoryNov 16 20:29:10 freeipa02.west.example
systemd[1]: dirsrv(a)EXAMPLE.NET.service failed to run 'start-pre' task: No such
file or directoryNov 16 20:29:10 freeipa02.west.example systemd[1]: Failed to start 389
Directory Server EXAMPLE.NET..Nov 16 20:29:10 freeipa02.west.example systemd[1]:
dirsrv(a)EXAMPLE.NET.service failed.Nov 16 20:29:10 freeipa02.west.example systemd[1]:
Starting 389 Directory Server EXAMPLE.NET....[root@freeipa02 slapd-EXAMPLE-NET]#
All the files are there. I did a comparison to the 01 server.
Regards,Andrew