I’m having an issue that I cannot google my way out of for some reason. I had Ansible working just fine on all my systems but I hadn’t used it in a while. I went back to push some changes recently and now I cannot push anything…I can’t even ‘ansible ping’ anything. I can manually SSH into each host with just my ssh keys with no issue, but when I run my playbook I get a “unreachable”: true error message. Below is the ouput and I receive this output on any ansible playbook I run. I’ve also tested this from another system with the same result, so it must be a node configuration issue or something. Any direction would be appreciated.
run with -vvv and see the full ssh command, try to run that manually
and debug the issue from there.
When I run that command with -vvv I receive the exact same output.
If you’re asking to ping manually, that works. Using SSH into the client works too.
I'm having an issue that I cannot google my way out of for some reason. I
had Ansible working just fine on all my systems but I hadn't used it in a
while. I went back to push some changes recently and now I cannot push
anything...I can't even 'ansible ping' anything. I can manually SSH into
each host with just my ssh keys with no issue, but when I run my playbook I
get a "unreachable": true error message. Below is the ouput and I receive
this output on any ansible playbook I run. I've also tested this from
another system with the same result, so it must be a node configuration
issue or something. Any direction would be appreciated.
How long is "a while"? 
Maybe a more precise question is "what version of Ansible are you using?"
--g
When I run that command with -vvv I receive the exact same output.
If you're asking to ping manually, that works. Using SSH into the client
works too.
Could you supply the following information:
1. OS of the system you are running the command from
2. The version of the OS/kernel
3. The version of ansible you are running.
The nmuxserver_listen bind() error usually comes from the OS/kernel
'shutting' off access to the software. This can come from
apparmor/selinux/macos antivirus etc. There can be other problems..
but those were the ones I remember the most coming up.
If -vvv gives you the exact same output, there is something really
wrong with your version of Ansible.
About a month is what I would say that it was working and now it’s not. I’m using 2.2.1.0.
I’ve sold my issue…sort off…although I don’t know what caused it. My home directory is on a gluster file system and that has been updated in the past month. When I moved it over to a regular NFS system it all started working again. I guess it’s a gluster bug. 
Solved I mean…