[389-users] Re: 389 server stops after Ansible "hangs up"

2016-02-25 Thread Joshua J. Kugler
On Thursday, February 25, 2016 14:50:58 William Brown wrote: > > > What happens if you use the ansible service module with - IE: > > > > > > - name: Start dirsrv > > > sudo: yes > > > action: service enabled=yes state=restarted > > > > I will set it up and run it again, but the same

[389-users] Re: 389 server stops after Ansible "hangs up"

2016-02-24 Thread William Brown
> > What happens if you use the ansible service module with - IE: > > > > - name: Start dirsrv > >   sudo: yes  > >   action: service enabled=yes state=restarted  > > I will set it up and run it again, but the same thing happened. That's how I  > originally found it. Actually, I did it with

[389-users] Re: 389 server stops after Ansible "hangs up"

2016-02-23 Thread Joshua J. Kugler
On Wednesday, February 24, 2016 14:57:20 William Brown wrote: > Please do *not* use /etc/init.d scripts. You *must* use "service > " > > Invoking this (via an ansible shell command) fails to work correctly as > > well: > > > > - name: Start Dirsrv > > shell: nohup screen -d -m

[389-users] Re: 389 server stops after Ansible "hangs up"

2016-02-23 Thread William Brown
> > > > Can you please post the output of sudo ipactl restart. I am suspicious > > it's not a DS issue, but another component of IPA is failing that > > causes the dirsrv to stop.  > > > > Can you post the yml of the service command you were using? > > > > What version of EL are you running? 

[389-users] Re: 389 server stops after Ansible "hangs up"

2016-02-14 Thread William Brown
On Thu, 2016-02-11 at 23:08 -0800, Joshua J. Kugler wrote: > On Friday, February 12, 2016 15:41:28 William Brown wrote: > > On Thu, 2016-02-11 at 17:25 -0800, Joshua J. Kugler wrote: > > > William - > > > > > > Thanks for the tips. > > > > > > For my debugging, se linux is disabled, and this

[389-users] Re: 389 server stops after Ansible "hangs up"

2016-02-11 Thread Joshua J. Kugler
On Friday, February 12, 2016 15:41:28 William Brown wrote: > On Thu, 2016-02-11 at 17:25 -0800, Joshua J. Kugler wrote: > > William - > > > > 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

[389-users] Re: 389 server stops after Ansible "hangs up"

2016-02-11 Thread William Brown
On Thu, 2016-02-11 at 17:25 -0800, Joshua J. Kugler wrote: > William - > > 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

[389-users] Re: 389 server stops after Ansible "hangs up"

2016-02-11 Thread Joshua J. Kugler
William - 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. j On Friday, February 12, 2016 09:43:40 William Brown wrote: > On Thu,

[389-users] Re: 389 server stops after Ansible "hangs up"

2016-02-11 Thread William Brown
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

[389-users] Re: 389 server stops after Ansible "hangs up"

2016-02-11 Thread Todor Petkov
On 2/11/2016 5:44 PM, 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 Hello, could be unrelated, but check if the server crashes from TLS 1.2 connections. I had this