On 02/11/2016 10:44 AM, Joshua J. Kugler wrote:
Cross post from the ansible list, to see if anyone here has any clue
Ansible 2.0.0.2
Control host: Ubuntu 14.04
Controlled host: CentOS 6
So, I've been trying to set up FreeIPA on my CentOS. I was getting really
frustrated because right after ipa-server-install completed successfully, and
I ran /etc/init.d/ipa start, subsequent commands failed. I finally realized
that dirsrv (389 LDAP server) was stopping soon after starting.
Joshua,
Can you post the Directory Server's errors log:
/var/log/dirsrv/slapd-INSTANCE/errors
Also the version of the Directory Server: rpm -qa | grep 389-ds-base
If you see in the Directory Server's errors log: "Detected Disorderly
Shutdown" then the server is crashing. To further troubleshoot the
crash(if there is one) please follow:
http://www.port389.org/docs/389ds/FAQ/faq.html#sts=Debugging%C2%A0Crashes
Then reproduce the crash, and post some stacktraces from the core file
to this list.
Thanks,
Mark
Thinking there was something odd in the ipa startup, I started IPA, slept for
30 seconds, and then tried to start dirsrv. That reported that dirsrv was
already running...but then it shut down right away. Logging in to the machine
and starting dirsrv was fine. Starting dirsrv via
ssh <host> "/etc/init.d/dirsrv start"
also worked.
So, I put this in my Ansible command:
shell: /etc/init.d/dirsrv start && sleep 30
The logs show dirsrv start. And stay started. As soon as that sleep 30
expires, however, and ansible "hangs up" the server immediately shuts down.
Same if I try:
command: /etc/init.d/dirsrv start && sleep 30
Same problem if I wrap the thing in a "script:" command.
WHAT would be killing a daemon, started by an init.d script, to shut down
(cleanly, no less) when ansible is done with the command and disconnects. And
the command to start IPA (or just the server, in the case of chasing down the
bug) is followed by other ansible commands for that host, so it's not like
ansible is done with the host when it "hangs up" after the given command.
I am at my wits end. Does anyone have any ideas how to fix or work around it? I
even tried wrapping the init.d/ipa start in a
screen -d -m
session, but that shuts down right away.
Interestingly enough, if I put this in a script:
#!/bin/bash
screen -d -m /etc/init.d/ipa start /etc/init.d/ipa start
sleep 30
And then pass that to the "screen background" process, even though it has gone
into the background, Ansible won't continue until the script ends and the
screen session terminates...but the dirsrv does stop right away!
So, something truly weird is going on here. Clearly a bug on the dirsrv side,
but a really weird interaction with ansible and its ssh sessions.
Ideas would be greatly appreciated!
j
--
389 users mailing list
389-users@%(host_name)s
http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
