Since you're backgrounding the script, the shell will finish immediately. Not sure why this would be stopping you're script from running.
If your script finishes when all of the instances are started, just remove the & at the end and run it in the foreground. Ansible will wait for it to return. On Thursday, June 8, 2017 at 8:44:38 AM UTC+10, Surya wrote: > > Dear Ansible Team, > > I have my customized Jboss start script "jboss-start-all.sh" to start my > Domain/host controllers and the server groups. When i execute the the > script locally its starting the instances successfully. but when i trigger > it from ansible, the command is successfully executed but the instances are > not starting . > > - name: Start Jboss EAP Server > shell: "nohup /opt/jboss-eap-6.4/bin/jboss-start-all.sh &" > tags: start > > is it possible to keep the ansible session active till the script is > starting all the instances. What i suspect is, Ansible fire the command in > remote server and closing the session, As soon as session is closed my > script also stopped, so its failing to start all my instances. > > Please help fix this issue. > -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/06695bfc-26cd-490a-a4da-0883cbbddd7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
