# supervisorctl module

**URL:** <https://forum.ansible.com/t/supervisorctl-module/13824>\
**Category:** Ansible Developer\
**Created:** [November 1, 2013, 3:01pm UTC](https://forum.ansible.com/t/supervisorctl-module/13824 "2013-11-01T15:01:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_Jarvis](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@John\_Jarvis](https://forum.ansible.com/u/John_Jarvis)\
**Post date:** [November 1, 2013, 3:01pm UTC](https://forum.ansible.com/t/supervisorctl-module/13824/1 "2013-11-01T15:01:57Z")

</div>

For those who use this module I was wondering if you could give some  
feedback on this open issue  
[https://github.com/ansible/ansible/issues/4707](https://github.com/ansible/ansible/issues/4707) ?

In general, I've been having a lot of problems with supervisor due to  
this issue - [https://github.com/Supervisor/supervisor/issues/48](https://github.com/Supervisor/supervisor/issues/48)

Where failures can be unpredictable depending on whether restarts and  
service restarts happen right after each other. I think moving away  
from service restarts of supervisord is the way to go and instead let  
the module restart supervisord when a parameter is set and make sure  
its fully up before starting services.

Is anyone else running into similar problems?

-John