# Ansible 0.8 error on Centos5 "TypeError: connect() got an unexpected keyword argument 'transport'"

**URL:** <https://forum.ansible.com/t/ansible-0-8-error-on-centos5-typeerror-connect-got-an-unexpected-keyword-argument-transport/12018>\
**Category:** Ansible Project\
**Created:** [October 23, 2012, 9:05pm UTC](https://forum.ansible.com/t/ansible-0-8-error-on-centos5-typeerror-connect-got-an-unexpected-keyword-argument-transport/12018 "2012-10-23T21:05:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Coddington](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Matt\_Coddington](https://forum.ansible.com/u/Matt_Coddington)\
**Post date:** [October 23, 2012, 9:05pm UTC](https://forum.ansible.com/t/ansible-0-8-error-on-centos5-typeerror-connect-got-an-unexpected-keyword-argument-transport/12018/1 "2012-10-23T21:05:15Z")

</div>

Hi all,  
I feel like I must be doing something wrong here, but I just pulled  
0.8 from github and am running into the following error in the  
"GATHERING FACTS" phase. My server system is Centos 5.6 (and was  
working fine with ansible 0.7 prior to my update). Can anyone point  
me towards what might be going wrong here?

thanks!  
matt

[17:01]walutil1 /ansible/ansible# cat VERSION  
0.8  
[17:01]walutil1 /ansible/ansible# . hacking/env-setup  
PATH=/rbi/ansible/ansible/bin:/rbi/ansible/ansible/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/bin:/bin  
PYTHONPATH=/rbi/ansible/ansible/lib:/rbi/ansible/ansible/lib:  
ANSIBLE\_LIBRARY=/rbi/ansible/ansible/library  
MANPATH=/rbi/ansible/ansible/docs/man:/rbi/ansible/ansible/docs/man:  
Reminder: specify your host file with -i  
Done.  
[17:01]walutil1 /ansible/ansible# cat /ansible/conf/test/test2

---

<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:** [October 23, 2012, 9:22pm UTC](https://forum.ansible.com/t/ansible-0-8-error-on-centos5-typeerror-connect-got-an-unexpected-keyword-argument-transport/12018/2 "2012-10-23T21:22:12Z")

</div>

It is finding old modules from another install.

-- Michael

---

<div class="post-metadata">

**Author:** ![Matt\_Coddington](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Matt\_Coddington](https://forum.ansible.com/u/Matt_Coddington)\
**Post date:** [October 24, 2012, 2:55am UTC](https://forum.ansible.com/t/ansible-0-8-error-on-centos5-typeerror-connect-got-an-unexpected-keyword-argument-transport/12018/3 "2012-10-24T02:55:38Z")

</div>

> It is finding old modules from another install.

Thanks Michael... I must have gotten something wrong merging. I've  
done clean checkout and re-merged with the couple local changes i have  
and all is well.

thanks again,  
matt

---

<div class="post-metadata">

**Author:** ![Matt\_Coddington](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Matt\_Coddington](https://forum.ansible.com/u/Matt_Coddington)\
**Post date:** [October 24, 2012, 3:08am UTC](https://forum.ansible.com/t/ansible-0-8-error-on-centos5-typeerror-connect-got-an-unexpected-keyword-argument-transport/12018/4 "2012-10-24T03:08:51Z")

</div>

> > It is finding old modules from another install.
> 
> Thanks Michael... I must have gotten something wrong merging. I've  
> done clean checkout and re-merged with the couple local changes i have  
> and all is well.

One last update here as maybe it will help someone in the future who  
gets a similar error and finds this thread... turns out the problem  
wasn't my merge, it was old .pyc's hanging around. I reproduced the  
problem at another site just now and a "find . -name '\*.pyc' -exec rm  
{} \;" fixed it.

matt