Thanks for the tips.
For my debugging, se linux is disabled, and this issue happens even if I leave
IPA out of it: if I just do /etc/init.d/dirsrv start, it then shuts down when
the ansible connection closes.
On Friday, February 12, 2016 09:43:40 William Brown wrote:
On Thu, 2016-02-11 at 14:44 -0800, Joshua J. Kugler wrote:
> Here is the entire log from 'errors'. It starts up just fine, then
> Ansible disconnects, something shuts it down. Is the dirsrv startup
> not properly applying NOHUP or some such? The REALLY weird thing is
> that this
> works properly with an interactive ssh login, or with
> ssh <host> "/etc/init.d/ipa start"
Please do NOT use /etc/init.d/ scripts as they do not set the SELinux
context correctly. You need to use "service <name> <action>" else
may be creating SELinux issues with your daemons.
Are you running EL6 or el7?
sudo ipactl restart
That may give you a hint as to what service has the issue
For example, when I have IPA issues, it tends to be DNS, and it's only
when the SMB process tries to start that it fails.
So when smb fails, then ipactl unwinds and shuts down all the OTHER
So you may find the issue isn't Ds, but some other part of freeipa.
I hope that helps you solve the issue.
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
joshua(a)azariah.com - Jabber: pedahzur(a)gmail.com
PGP Key: http://pgp.mit.edu/