# ansible connection issue on remote RHE5 linux server **URL:** \ **Category:** Ansible Project\ **Tags:** awx\ **Created:** [February 2, 2023, 5:02am UTC](https://forum.ansible.com/t/ansible-connection-issue-on-remote-rhe5-linux-server/37608 "2023-02-02T05:02:37Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![anish\_kumar2](https://avatars.discourse-cdn.com/v4/letter/a/a88e4f/32.png) [@anish\_kumar2](https://forum.ansible.com/u/anish_kumar2)\ **Post date:** [February 2, 2023, 5:02am UTC](https://forum.ansible.com/t/ansible-connection-issue-on-remote-rhe5-linux-server/37608/1 "2023-02-02T05:02:37Z")
I am running the ansible playbook through AWX and its getting failed with the subjected error. But same playbook is running on another server successfully. Kindly help to resolve the issue. Successful login on sever :- os config Redhat enterprise linux 7.9 Error while login on server:- os config Redhat enterprise linux 5.0 Error :- fatal localhost-\>192.168.101.12]: FAILED! =\> changed": false, “module\_stderr”: “Shared connection to 192.168.101.12]closed in”, “module.stdout”:"File W/home/web/ak1/ansible/tmp/ansible-tmp-1675175673.3860075-51234- 280095385528185/AnsiballZ\_command.py", line 72n with open(args.path. 'rb) as fin “Ventadmor invalid syntaxin”, “msg”: "MODULE FAILURE\See stdout/stderr for the exact error, “rc”:1} ---
**Author:** ![dnmvisser](https://avatars.discourse-cdn.com/v4/letter/d/8e8cbc/32.png) [@dnmvisser](https://forum.ansible.com/u/dnmvisser)\ **Post date:** [February 2, 2023, 5:57am UTC](https://forum.ansible.com/t/ansible-connection-issue-on-remote-rhe5-linux-server/37608/2 "2023-02-02T05:57:18Z")
upgrade your server ---
**Author:** ![Akasurde](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akasurde/32/230_2.png) [@Akasurde](https://forum.ansible.com/u/Akasurde)\ **Post date:** [February 2, 2023, 6:49am UTC](https://forum.ansible.com/t/ansible-connection-issue-on-remote-rhe5-linux-server/37608/3 "2023-02-02T06:49:08Z")
Please upgrade your RHEL 5 machine to the latest RHEL version. ---
**Author:** ![Nico\_Kadel-Garcia](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nico_kadel-garcia/32/9998_2.png) [@Nico\_Kadel-Garcia](https://forum.ansible.com/u/Nico_Kadel-Garcia)\ **Post date:** [February 2, 2023, 7:26am UTC](https://forum.ansible.com/t/ansible-connection-issue-on-remote-rhe5-linux-server/37608/4 "2023-02-02T07:26:08Z")
People don't always have such choices immediately in hand, especially when expensive or obsolete software with vital services have no budget for replacement. That's been a lot of my career, and my increasingly expensive consulting or salaried work. Anish, it sounds like you need to have a chat with your SSH configurations. OpenSSH has evolved and older, less secure encryption protocols have been discarded. Validate that your SSH based logins work from the command line, from your RHEL 7.9 server, to the RHEL 5 server, and folks are right. You should \*really\* update that system to something still supported, if you can. Extended life cycle support for RHEL 5 ended in 2020, things are going to get worse iover time if you keep trying to keep that going. Nico Kadel-Garcia ---
**Author:** ![Akasurde](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/akasurde/32/230_2.png) [@Akasurde](https://forum.ansible.com/u/Akasurde)\ **Post date:** [February 2, 2023, 7:28am UTC](https://forum.ansible.com/t/ansible-connection-issue-on-remote-rhe5-linux-server/37608/5 "2023-02-02T07:28:40Z")
+1 Nico ---
**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:** [February 2, 2023, 12:56pm UTC](https://forum.ansible.com/t/ansible-connection-issue-on-remote-rhe5-linux-server/37608/6 "2023-02-02T12:56:39Z")
I built the most current (at the time) Python and installed the Python executable in my home directory, then I used an Ansible variable in my inventory file (I don’t remember which variable) to specify an alternate Python interpreter and things were fine when I had an old Python interpreter on a remote system. Mike ---
**Author:** ![Nico\_Kadel-Garcia](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nico_kadel-garcia/32/9998_2.png) [@Nico\_Kadel-Garcia](https://forum.ansible.com/u/Nico_Kadel-Garcia)\ **Post date:** [February 2, 2023, 10:39pm UTC](https://forum.ansible.com/t/ansible-connection-issue-on-remote-rhe5-linux-server/37608/7 "2023-02-02T22:39:56Z")
Until they're not. Provenance, compatibility, and consistency of python modules in different python builds can depend on a lot of factors, such as previously installed components detected at build time and regressions in updated components. It works until it doesn't, and the fix may be neither obvious, simple, nor local. It's why I'm such a strong advocate of packaging ansible tools rather than doing "pip install" with gods only know what the base python version might be and what is in pypi.org at this moment.