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}
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.
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.
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.