# Timeout property not working on Monit Module

**URL:** <https://forum.ansible.com/t/timeout-property-not-working-on-monit-module/30607>\
**Category:** Ansible Project\
**Created:** [June 19, 2019, 6:56pm UTC](https://forum.ansible.com/t/timeout-property-not-working-on-monit-module/30607 "2019-06-19T18:56:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jourdan\_West](https://avatars.discourse-cdn.com/v4/letter/j/22d042/32.png) [@Jourdan\_West](https://forum.ansible.com/u/Jourdan_West)\
**Post date:** [June 19, 2019, 6:56pm UTC](https://forum.ansible.com/t/timeout-property-not-working-on-monit-module/30607/1 "2019-06-19T18:56:36Z")

</div>

Hello,

I’m using Ansible’s [Monit module](https://docs.ansible.com/ansible/latest/modules/monit_module.html), to restart a service like so:

`  
name: restart resque-x (monit)  
monit:  
name: resque-x  
state: restarted

`

The issue is that it doesn’t wait for the process to restart (needs about 30 secs) and immediately returns the following error:

> **resque-x process not presently configured with monit**

A few points here:

1. When I actually observe monit activity on the managed node, I clearly see service resque-x being stopped and started. So the error message is verified to be incorrect.
2. The docs indicate that the module will wait a default 300 seconds for the operation to complete. That is **not** happening.
3. I also tried to explicitly define the timeout attribute. It had no impact on the behavior on the above task.

Please advise.
