There are no firewall rules that I can see. All installations of ansible 
was done by ssh-ing to that host, so ssh port is definitely open.
*# sudo iptables -L*
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


*#  netstat -tupln | grep ":22 "*
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   
LISTEN      8969/sshd
tcp        0      0 :::22                       :::*                       
 LISTEN      8969/sshd

On Monday, January 4, 2016 at 7:12:24 PM UTC-5, Chun-Hung Huang wrote:
>
> Any firewall rule with your local machine?
> --- in linux try to check your firewall 
> $ sudo iptables -L 
>
> Check /etc/hosts.allow and /etc/hosts.deny
>
> Does port 22 open in your local machine?
> $ netstat -tupln 
>
> ^^
>
>
> Ravi B於 2016年1月5日星期二 UTC+8上午12時27分04秒寫道:
>>
>> Hi everyone,
>>     I'm new to ansible and trying to get the basing ping working on local 
>> host (127.0.0.1 in the $ANSIBLE_HOSTS file) but keep running into 
>> problems.I thought the problem was python3 that was installed on the 
>> machine, but I uninstalled python3 (deleted the python3 binaries and 
>> reinstalled ansible from source). I'm still getting the same error with 
>> ansible (see the error below in red).
>> The command "ansible all -m ping" is not working.
>>
>> # python -V
>> Python 2.7.11
>>
>> # pip install --upgrade paramiko
>> Requirement already up-to-date: paramiko in 
>> /usr/local/lib/python2.7/site-packages/paramiko-1.16.0-py2.7.egg
>> Requirement already up-to-date: pycrypto!=2.4,>=2.1 in 
>> /usr/local/lib/python2.7/site-packages/pycrypto-2.6.1-py2.7-linux-x86_64.egg 
>> (from paramiko)
>> Requirement already up-to-date: ecdsa>=0.11 in 
>> /usr/local/lib/python2.7/site-packages/ecdsa-0.13-py2.7.egg (from paramiko)
>>
>> # cat $ANSIBLE_HOSTS
>> 127.0.0.1
>>
>> # ansible --version
>> ansible 1.9.4
>>   configured module search path = None
>>
>> *# ansible all -m ping*
>> *No handlers could be found for logger "paramiko.transport"*
>> *127.0.0.1 | FAILED => FAILED: Error reading SSH protocol banner[Errno 
>> 104] Connection reset by peer*
>>
>> *I'm getting the same error with ansible 2 also*
>> # ansible --version
>> ansible 2.1.0
>>   config file =
>>   configured module search path = Default w/o overrides
>>
>> # ansible all -m ping
>> No handlers could be found for logger "paramiko.transport"
>> 127.0.0.1 | UNREACHABLE! => {
>>     "changed": false,
>>     "msg": "ERROR! Error reading SSH protocol banner[Errno 104] 
>> Connection reset by peer",
>>     "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/97d26920-05c0-4540-8ac3-2885071cdaf3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to