# Problems with ans-comman wrapper with --forks \> 1

**URL:** <https://forum.ansible.com/t/problems-with-ans-comman-wrapper-with-forks-1/11312>\
**Category:** Ansible Project\
**Created:** [February 29, 2012, 1:09am UTC](https://forum.ansible.com/t/problems-with-ans-comman-wrapper-with-forks-1/11312 "2012-02-29T01:09:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [February 29, 2012, 1:09am UTC](https://forum.ansible.com/t/problems-with-ans-comman-wrapper-with-forks-1/11312/1 "2012-02-29T01:09:26Z")

</div>

CentOS 5, IIRC:

[root@localhost ansible]# ./bin/ans-command /bin/true  
/bin/true  
127.0.0.1:

Traceback (most recent call last):  
File “/usr/lib64/python2.6/multiprocessing/queues.py”, line 233, in \_feed  
debug(‘feeder thread got sentinel – exiting’)  
TypeError: ‘NoneType’ object is not callable

ansible -n command -a /bin/true -f 1 seems to work

[root@localhost ansible]# ./bin/ans-command /bin/echo hi  
FORKS=3  
/bin/echo hi  
127.0.0.1:  
hi

Exception in thread QueueFeederThread (most likely raised during  
interpreter shutdown):  
Traceback (most recent call last):  
File “/usr/lib64/python2.6/threading.py”, line 532, in \_\_bootstrap\_inner  
File “/usr/lib64/python2.6/threading.py”, line 484, in run  
File “/usr/lib64/python2.6/multiprocessing/queues.py”, line 233, in \_feed  
\<type ‘exceptions.TypeError’\>: ‘NoneType’ object is not callable

Ideas?

–Michael

---

<div class="post-metadata">

**Author:** ![Seth\_Vidal](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@Seth\_Vidal](https://forum.ansible.com/u/Seth_Vidal)\
**Post date:** [February 29, 2012, 1:27am UTC](https://forum.ansible.com/t/problems-with-ans-comman-wrapper-with-forks-1/11312/2 "2012-02-29T01:27:59Z")

</div>

Not right off. I run mine with the default fork count of 3 all the time.

How many hosts are you connecting to?

Just 1?

I have 2 hosts I communicate with - I'll test it with just one - see if  
it causes it.

-sv