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.

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

-- 
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
[email protected] - Jabber: [email protected]
PGP Key: http://pgp.mit.edu/  ID 0x73B13B6A

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/72762047.2gWIYo0p4b%40hosanna.
For more options, visit https://groups.google.com/d/optout.

Reply via email to