Solved I mean...
On Wednesday, April 12, 2017 at 5:54:37 PM UTC-5, Mike Johnston wrote:
>
> 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. :/
>
> On Tuesday, April 11, 2017 at 6:11:35 PM UTC-5, Mike Johnston wrote:
>>
>> 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.
>>
>> ################
>> [mijohnst@server1]# ansible all -m ping --ask-pass
>>
>> server1 | UNREACHABLE! => {
>> "changed": false,
>> "msg": "Failed to connect to the host via ssh: \nmuxserver_listen
>> bind(): Permission denied\r\n",
>> "unreachable": true
>> }
>> ################
>>
>>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/5201e837-e72b-40d7-80d1-786a554c1e05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
