# make install problem

**URL:** <https://forum.ansible.com/t/make-install-problem/12214>\
**Category:** Ansible Project\
**Created:** [January 19, 2013, 4:36am UTC](https://forum.ansible.com/t/make-install-problem/12214 "2013-01-19T04:36:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patric\_Buskas](https://avatars.discourse-cdn.com/v4/letter/p/ba8739/32.png) [@Patric\_Buskas](https://forum.ansible.com/u/Patric_Buskas)\
**Post date:** [January 19, 2013, 4:36am UTC](https://forum.ansible.com/t/make-install-problem/12214/1 "2013-01-19T04:36:30Z")

</div>

Hi,

I was trying to install ansible by following the “Make Install” instruction on the Getting started page but I can’t make it work.  
I’m getting this “says-me-nothing”-error:

patric@micro:~/git/ansible$ ansible 127.0.0.1 -m ping  
127.0.0.1 | FAILED =\> Traceback (most recent call last):  
File “_/usr/local/lib/python2.7/dist-packages/ansible/runner/_ **init**.py”, line 237, in \_executor  
exec\_rc = self.\_executor\_internal(host)  
File “_/usr/local/lib/python2.7/dist-packages/ansible/runner/_ **init**.py”, line 293, in \_executor\_internal  
return self.\_executor\_internal\_inner(host, self.module\_name, self.module\_args, inject, port)  
File “_/usr/local/lib/python2.7/dist-packages/ansible/runner/_ **init**.py”, line 408, in \_executor\_internal\_inner  
tmp = self.\_make\_tmp\_path(conn)  
File “_/usr/local/lib/python2.7/dist-packages/ansible/runner/_ **init**.py”, line 510, in \_make\_tmp\_path  
result = self.\_low\_level\_exec\_command(conn, cmd, None, sudoable=False)  
File “_/usr/local/lib/python2.7/dist-packages/ansible/runner/_ **init**.py”, line 448, in \_low\_level\_exec\_command  
rc, stdin, stdout, stderr = conn.exec\_command(cmd, tmp, sudo\_user, sudoable=sudoable, executable=executable)  
TypeError: exec\_command() got an unexpected keyword argument ‘executable’

When I run “from checkout” with sourcing the env-setup everything works just fine  
Am I reading the getting started instruction wrong or is something broken?

BR  
/Patric

---

<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:** [January 19, 2013, 1:47pm UTC](https://forum.ansible.com/t/make-install-problem/12214/2 "2013-01-19T13:47:27Z")

</div>

Do you have some mix of things running from checkout and files in the  
OS install, possibly?

---

<div class="post-metadata">

**Author:** ![CWS](https://avatars.discourse-cdn.com/v4/letter/c/e495f1/32.png) [@CWS](https://forum.ansible.com/u/CWS)\
**Post date:** [February 4, 2013, 6:20pm UTC](https://forum.ansible.com/t/make-install-problem/12214/3 "2013-02-04T18:20:12Z")

</div>

I ran into a similar issue upgrading from 0.7-devel (which in turn was upgraded in various stages up from 0.4) to 1.0. The problem is that there are some old /usr/local/lib/python2.7/dist-packages/ansible/runner/connection/ files left, which from what I gather at a glance now live in /usr/local/lib/python2.7/dist-packages/ansible/runner/connection\_plugins/ . The former (older) were overriding the latter (newer) and they were missing the optional ‘executable’ parameter.

Solution: (re)move /usr/local/lib/python2.7/dist-packages/ansible and run make install again.