# Problems becoming root on Multi-Tech mlinux

**URL:** <https://forum.ansible.com/t/problems-becoming-root-on-multi-tech-mlinux/24356>\
**Category:** Ansible Project\
**Created:** [April 29, 2017, 12:59pm UTC](https://forum.ansible.com/t/problems-becoming-root-on-multi-tech-mlinux/24356 "2017-04-29T12:59:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeffrey\_Honig](https://avatars.discourse-cdn.com/v4/letter/j/7993a0/32.png) [@Jeffrey\_Honig](https://forum.ansible.com/u/Jeffrey_Honig)\
**Post date:** [April 29, 2017, 12:59pm UTC](https://forum.ansible.com/t/problems-becoming-root-on-multi-tech-mlinux/24356/1 "2017-04-29T12:59:42Z")

</div>

I’m using Ansible to CM Multi-Tech Conduits running mLinux. It’s a Yocto Project based Linux and /bin/sh points to /bin/bash. It has su, but does not have sudo.

Ansible can ping the box if ansible\_user is a normal user.

Ansible can ping the box if ansible\_user is root.

Ansible can not ping the box if I configure ping to use become = yes, become\_method = su. I get a timeout error.

I’ve run the individual commands that Ansible uses for ping (i.e. ping.py) and it does work.

I suspect this has something to do with the handling of the Password: prompt. Any tips for debugging this?

Thanks.

Jeff

---

<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:** [May 1, 2017, 6:27pm UTC](https://forum.ansible.com/t/problems-becoming-root-on-multi-tech-mlinux/24356/2 "2017-05-01T18:27:14Z")

</div>

You are likely suffering from the situation that the following PR has recently fixed:

[https://github.com/ansible/ansible/pull/23710](https://github.com/ansible/ansible/pull/23710)