Thanks Kai for that insight , i have taken out the port=22 and include the
timeout=600 option in wait_for module  in  order to check the services by
login to server. Also can we set different timeout values for different
host in wait_for module.Can you please throw some light as i am created a
playbook for reboot and calling it in other playbook by specifying specific
host. like below but its not working .

---
 tasks:
   shell: sleep 2 && shutdown -r now
   async: 1
   poll: 0
   ignore_errors: true

server.yml

---
- name: for the individual hosts
- hosts: 192.168.3.154 <========( This server requires to wait for the
server to come online after reboot )
  tasks:
   include: tasks/restart1.yml
   - name: wait for the server to be online
     local_action: wait_for host={{ inventory_hostname }} state=started
delay=5 timeout=120

- hosts: 192.168.3.153 <============ ( this server doesnot require to wait
for the server to come back after reboot )
  tasks:
   - include: tasks/restart1.yml


But its giving me the syntax errors including error of duplicate tasks etc.

Thanks for helping



On Tue, Nov 7, 2017 at 11:20 PM, Kai Stian Olstad <
[email protected]> wrote:

> On 07. nov. 2017 18:22, coach rhca wrote:
> > Thanks Kai , looking for something like the server is rebooted and looks
> > for the processes or service and then move to the next server reboots and
> > check the service and goes to  the next hosts and does the same.
>
> You can do something like this.
>
>   - shell: sleep 2 && /sbin/shutdown -r now
>     async: 1
>     poll: 0
>
>   - wait_for:
>       port: 22
>       host: '{{ inventory_hostname }}'
>       search_regex: OpenSSH
>       delay: 10
>     delegate_to: localhost
>
>   - service:
>       name: service-name
>       state: started
>     check_mode: yes
>     register: r
>
>   - fail:
>       msg: Something went wrong
>     when: r.state != 'started'
>
>
> But if your process is listening on a port that you can check, then you
> can use wait_for directly.
>
>
> --
> Kai Stian Olstad
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Ansible Project" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/ansible-project/5UvPWbQGyT4/unsubscribe.
> To unsubscribe from this group and all its topics, 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/400495c5-da75-5922-2e2a-9e07773cb68c%40olstad.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALguqPK04q6TkUzNbmTacUk6cjMoDKT-aO-LOrvHyzspQ4m%2Bkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to