Ansible baby steps failure. Can’t even ‘-m ping’ ;-( I’m a first time Ansible user and starting from the beginning. The first real task from the Introduction to Ansible is a connectivity test. After setting everything up the ping is bailing out on me with this generic error message: "msg": "…

Super dumb question Np. When it’s a bit late, dumb questions are forgiven :wink: So the day before yesterday I tracked it down as a Python incompatibility between the Python version on the Ansible controller and the system wide Python version on the node. [rant] I hate it when there’s no obvio…

It may be helpful to tell us what Ansible command string you were running. Assuming that you are using the ping module, it should look like this: ➜ tmp ansible -i inventory -m ping serverb [WARNING]: Platform linux on host serverb is using the discovered Python interpreter at /usr/bin/pytho…

Apologies for the missing command. I’m running: $ ansible -i inventory monitor.lan -m ping The outcome is the same for root and non-root. I’ve tried it against other servers in my small home network. I’ve got the following node results: Leap 15.4: OK Leap 15.5: Fail Leap 15.6: Fail Leap 15.6: OK …

TL;DR What OS are you logging into and as what user and what shell is that user configured with? run grep $USER /etc/passwd and the last item in the output should be your shell. If the echo command is not found, you’re probably using a very limited shell on a system with very limited commands av…

[image] Dylan_Martin3: TL;DR What OS are you logging into and as what user and what shell is that user configured with? See earlier posts: I’ve already increased the nodes tested against: All users are regular users. I did think of security settings. openSUSE is transitioning from AppAr…

Hmm… maybe I’m chasing a red herring with the ‘bash-sh-echo’ thing. In the debug log of one of the failing nodes I’m seeing: debug1: auto-mux: Trying existing master at \'/home/koos/.ansible/cp/e204b56f4e\' debug2: fd 3 setting O_NONBLOCK debug2: mux_client_hello_exchange: master version 4 debug3:…

Sorry, it’s a bit late. Super dumb question: Can you ssh into the target box without Ansible and run “echo foo”?

The issue with the echo ~ && sleep 0 command in Ansible’s SSH connectivity test likely stems from a misconfigured shell environment or Python incompatibility on the target node. To resolve this, ensure the default shell on the target machine (monitor.lan) is correctly set to /bin/bash (verify with g…

The long version is that I’ve discoverd that Ansible tells you what it supports if you run ansible-config list|grep -i python On the drone node I had Python v3.6 from the distribution. I installed 3.11 along side. That solved everything on the controller node.

Thanks! See my other post for the final update.

Problem with "echo ~ && sleep 0"

Get Help

rilindo (Rilindo Foster) July 1, 2025, 9:15pm 9

What was the difference that caused Ansible to fail?

Topic		Replies	Views
could not SSH to Cisco using CentOS Ansible Project	1	25	July 6, 2017
How to write an Ansible Module that does not do the initial check '/bin/sh -c '"'"'echo ~ && sleep 0'"'"'' Ansible Project	1	53	April 3, 2019
Stumped on ssh not connecting Ansible Project ubuntu	4	29	July 30, 2013
Ansible ssh problem (with pfsense) Ansible Project	1	40	August 28, 2023
module_stdout": "/bin/sh: 1: /usr/bin/python: not found\r\n Ansible Developer ubuntu	0	23	December 22, 2016

Problem with "echo ~ && sleep 0"

Related topics