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 > when > Ansible disconnects, something shuts it down. Is the dirsrv startup > script > 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 you may be creating SELinux issues with your daemons. Are you running EL6 or el7? Try: 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 services. So you may find the issue isn't Ds, but some other part of freeipa. I hope that helps you solve the issue. -- Sincerely, William Brown Software Engineer Red Hat, Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
-- 389 users mailing list 389-users@%(host_name)s http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
