Please disregard for now. I compared it to another server and found that
dir...@example.net is incorrect.
On Friday, November 16, 2018 2:46 PM, Andrew Meyer via FreeIPA-users
<freeipa-users@lists.fedorahosted.org> wrote:
I just noticed that I have 2 dirsrv systemctl units as well.
See below:
[root@freeipa02 slapd-EXAMPLE-NET]# systemctl list-units |grep -i dirsrv
dirsrv@EXAMPLE-NET.service loaded active
running 389 Directory Server EXAMPLE-NET.● dir...@example.net.service
loaded failed failed 389 Directory Server
EXAMPLE.NET. system-dirsrv.slice
loaded active active system-dirsrv.slice dirsrv.target
loaded active active 389 Directory
Server[root@freeipa02 slapd-EXAMPLE-NET]#
On Friday, November 16, 2018 2:40 PM, Andrew Meyer via FreeIPA-users
<freeipa-users@lists.fedorahosted.org> wrote:
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 dir...@example.net -l●
dir...@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]: dir...@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
dir...@example.net.service entered failed state.Nov 16 20:27:46
freeipa02.west.example systemd[1]: dir...@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]: dir...@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]:
dir...@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_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.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.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org
_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.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.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org
_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.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.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org
