# Ansible has stopped working for me **URL:** \ **Category:** Ansible Project\ **Created:** [April 11, 2017, 4:53pm UTC](https://forum.ansible.com/t/ansible-has-stopped-working-for-me/24193 "2017-04-11T16:53:35Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Mike\_Johnston](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@Mike\_Johnston](https://forum.ansible.com/u/Mike_Johnston)\ **Post date:** [April 11, 2017, 4:53pm UTC](https://forum.ansible.com/t/ansible-has-stopped-working-for-me/24193/1 "2017-04-11T16:53:35Z")
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. ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [April 12, 2017, 1:36am UTC](https://forum.ansible.com/t/ansible-has-stopped-working-for-me/24193/2 "2017-04-12T01:36:06Z")
run with -vvv and see the full ssh command, try to run that manually and debug the issue from there. ---
**Author:** ![Mike\_Johnston](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@Mike\_Johnston](https://forum.ansible.com/u/Mike_Johnston)\ **Post date:** [April 12, 2017, 7:58pm UTC](https://forum.ansible.com/t/ansible-has-stopped-working-for-me/24193/3 "2017-04-12T19:58:06Z")
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. ---
**Author:** ![Greg\_DeKoenigsberg1](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@Greg\_DeKoenigsberg1](https://forum.ansible.com/u/Greg_DeKoenigsberg1)\ **Post date:** [April 12, 2017, 8:00pm UTC](https://forum.ansible.com/t/ansible-has-stopped-working-for-me/24193/4 "2017-04-12T20:00:11Z")
> 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 ---
**Author:** ![Stephen\_John\_Smoogen](https://avatars.discourse-cdn.com/v4/letter/s/ad7895/32.png) [@Stephen\_John\_Smoogen](https://forum.ansible.com/u/Stephen_John_Smoogen)\ **Post date:** [April 12, 2017, 9:12pm UTC](https://forum.ansible.com/t/ansible-has-stopped-working-for-me/24193/5 "2017-04-12T21:12:21Z")
> 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. ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [April 12, 2017, 9:17pm UTC](https://forum.ansible.com/t/ansible-has-stopped-working-for-me/24193/6 "2017-04-12T21:17:56Z")
If -vvv gives you the exact same output, there is something really wrong with your version of Ansible. ---
**Author:** ![Mike\_Johnston](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@Mike\_Johnston](https://forum.ansible.com/u/Mike_Johnston)\ **Post date:** [April 12, 2017, 10:54pm UTC](https://forum.ansible.com/t/ansible-has-stopped-working-for-me/24193/7 "2017-04-12T22:54:37Z")
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. 😕 ---
**Author:** ![Mike\_Johnston](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@Mike\_Johnston](https://forum.ansible.com/u/Mike_Johnston)\ **Post date:** [April 12, 2017, 10:55pm UTC](https://forum.ansible.com/t/ansible-has-stopped-working-for-me/24193/8 "2017-04-12T22:55:49Z")
Solved I mean…