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

Archives Ansible Project
1

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

2

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