# error using "become"?

**URL:** <https://forum.ansible.com/t/error-using-become/31307>\
**Category:** Ansible Project\
**Created:** [September 18, 2019, 2:15pm UTC](https://forum.ansible.com/t/error-using-become/31307 "2019-09-18T14:15:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Eggleston](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Mike\_Eggleston](https://forum.ansible.com/u/Mike_Eggleston)\
**Post date:** [September 18, 2019, 2:15pm UTC](https://forum.ansible.com/t/error-using-become/31307/1 "2019-09-18T14:15:27Z")

</div>

GNU/Linux: CentOS Linux release 7.6.1810 (Core)

Playbook:

---

<div class="post-metadata">

**Author:** ![Mike\_Eggleston](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Mike\_Eggleston](https://forum.ansible.com/u/Mike_Eggleston)\
**Post date:** [September 18, 2019, 2:52pm UTC](https://forum.ansible.com/t/error-using-become/31307/2 "2019-09-18T14:52:28Z")

</div>

Removed Ansible 2.8.5 and installed Ansible 2.8.5.  
Same error.  
More simple playbook.  
Changed “become: yes” to “become:true”.  
Same error:

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [September 18, 2019, 2:56pm UTC](https://forum.ansible.com/t/error-using-become/31307/3 "2019-09-18T14:56:11Z")

</div>

What is the version of sudo installed on `appsrv98`?

I have a feeling that `appsrv98` is a really old machine, maybe running EL5 or something like that. In which case, even if you can get past the sudo issue, you’ll run into python version issues as well.

---

<div class="post-metadata">

**Author:** ![Mike\_Eggleston](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Mike\_Eggleston](https://forum.ansible.com/u/Mike_Eggleston)\
**Post date:** [September 18, 2019, 3:06pm UTC](https://forum.ansible.com/t/error-using-become/31307/4 "2019-09-18T15:06:09Z")

</div>

That’s an interesting thought.  
Ansible isn’t required on the remote machine; python is though.  
Here’s on the remote machine:

DEV App Server 98  
appsrv98:meggle1:/home/meggle1\> rpm -qi ansible  
package ansible is not installed  
DEV App Server 98  
appsrv98:meggle1:/home/meggle1\> python -V  
Python 2.7.16  
DEV App Server 98  
appsrv98:meggle1:/home/meggle1\>

---

<div class="post-metadata">

**Author:** ![Mike\_Eggleston](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Mike\_Eggleston](https://forum.ansible.com/u/Mike_Eggleston)\
**Post date:** [September 18, 2019, 3:21pm UTC](https://forum.ansible.com/t/error-using-become/31307/5 "2019-09-18T15:21:39Z")

</div>

Sudo is too old.  
This works:

---

<div class="post-metadata">

**Author:** ![Mike\_Eggleston](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Mike\_Eggleston](https://forum.ansible.com/u/Mike_Eggleston)\
**Post date:** [September 18, 2019, 3:24pm UTC](https://forum.ansible.com/t/error-using-become/31307/6 "2019-09-18T15:24:01Z")

</div>

Matt, thanks for your help.

Mike