My guess would be that your playbook tried to start it before it had 
finished shutting down.

Simplest thing to do would be wait a bit before trying the start, but it 
would be better to check it is down.

You could use wait_for module to check it is down:

Incidentally, checking that tomcat is fully up and ready to service 
requests is tricky as it seems to lock its listening port and then not 
respond on it for some time.

We used to just wait before polling a particular url but now we use a 
pattern similar to what is described here to poll until we get a 200!searchin/ansible-project/do-until$20with$20uri$20module%7Csort:relevance/ansible-project/iLjIbsCASWU/ZmE-wYdtLQAJ

Hope this helps,


On Thursday, September 15, 2016 at 4:10:11 PM UTC+1, 
> Hi,
> - hosts: dev_tomcat
>   vars:
>     http_port: 8080
>     sudo: true
>     sudo_user: build
>   tasks:
>   - name: copy_shut
>     copy: src=/etc/ansible/playbooks/scripts/ dest=/tmp
>   - name: change_permission_shut
>     file: path=/tmp/ mode=777
>   - name: copy_start
>     copy: src=/etc/ansible/playbooks/scripts/ dest=/tmp
>   - name: change_permission_start
>     file: path=/tmp/ mode=777
>   - name: stopping tomcat
>     shell: /tmp/./
>   - name: starting tomcat
>    #command: sudo -u build /etc/init.d/tomcat start
>     shell: /tmp/./
> => /etc/init.d/tomcat start
> ~
> Shutdown was happen properly, but it did not start tomcat, please advise 
> how to resolve this.
> Thanks,

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 post to this group, send email to
To view this discussion on the web visit
For more options, visit

Reply via email to