On Monday, February 15, 2016 07:51:11 William Brown wrote:
> 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 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.
> > >
> > > Are you using the ansible service module?
> >
> > I was. That's when I discovered the behavior. Also tried the ansible
> > shell and
> > command modules. Same thing.
>
> 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?
This is CentOS 6.7. I could post the output of 'sudo ipactl restart' but that
wouldn't show the problem.
1) If I'm logged in to a shell (SSH) it works
2) If I do it via "ssh host 'command'" it works
It is only when I invoke it via Ansible that it shows this behavior. Also
noted: it behaves this way just stand alone (see above). Using just
/etc/init.d/dirsrv start, it will shut down as soon as the connection goes
away. The attached log show the entire process from startup to shutdown.
Invoking this (via an ansible shell command) fails to work correctly as well:
- name: Start Dirsrv
shell: nohup screen -d -m /usr/sbin/start-dirsrv
So even trying to nohup + using screen to "background" it, it still shuts down
immediately after that 'shell' stanza is done.
Even this fails: nohup screen -d -m /usr/sbin/start-dirsrv & disown
The ansible output from just invoking /usr/sbin/start-dirsrv is:
changed: [192.168.122.12] => {"changed": true, "cmd": "/usr/sbin/start-
dirsrv", "delta": "0:00:02.760271", "end": "2016-02-11 12:40:15.909214", "rc":
0, "start": "2016-02-11 12:40:13.148943", "stderr": "", "stdout": "Starting
instance \"KUGLER-LOCALDOMAIN\"\nStarting instance \"PKI-IPA\"",
"stdout_lines": ["Starting instance \"KUGLER-LOCALDOMAIN\"", "Starting
instance \"PKI-IPA\""], "warnings": []}
So it successfully starts. No errors. But then shuts down right away.
j
--
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
joshua@xxxxxxxxxxx - Jabber: pedahzur@xxxxxxxxx
PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A[11/Feb/2016:12:29:59 -0900] - 389-Directory/1.2.11.15 B2016.040.940 starting up
[11/Feb/2016:12:29:59 -0900] schema-compat-plugin - warning: no entries set up under cn=computers, cn=compat,dc=kugler,dc=localdomain
[11/Feb/2016:12:29:59 -0900] schema-compat-plugin - warning: no entries set up under cn=ng, cn=compat,dc=kugler,dc=localdomain
[11/Feb/2016:12:29:59 -0900] schema-compat-plugin - warning: no entries set up under ou=sudoers,dc=kugler,dc=localdomain
[11/Feb/2016:12:29:59 -0900] - Skipping CoS Definition cn=Password Policy,cn=accounts,dc=kugler,dc=localdomain--no CoS Templates found, which should be added before the CoS Definition.
[11/Feb/2016:12:30:00 -0900] - Skipping CoS Definition cn=Password Policy,cn=accounts,dc=kugler,dc=localdomain--no CoS Templates found, which should be added before the CoS Definition.
[11/Feb/2016:12:30:00 -0900] - slapd started. Listening on All Interfaces port 389 for LDAP requests
[11/Feb/2016:12:30:00 -0900] - Listening on All Interfaces port 636 for LDAPS requests
[11/Feb/2016:12:30:00 -0900] - Listening on /var/run/slapd-KUGLER-LOCALDOMAIN.socket for LDAPI requests
[11/Feb/2016:12:30:02 -0900] - slapd shutting down - signaling operation threads
[11/Feb/2016:12:30:02 -0900] - slapd shutting down - closing down internal subsystems and plugins
[11/Feb/2016:12:30:02 -0900] - Waiting for 4 database threads to stop
[11/Feb/2016:12:30:02 -0900] - All database threads now stopped
[11/Feb/2016:12:30:02 -0900] - slapd stopped.
--
389 users mailing list
389-users@%(host_name)s
http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
