I believe we silenced some paramiko warnings earlier, though this also
seems to be a warning.
Did you install paramiko from RPM?
What version of ansible?
I believe we silenced some paramiko warnings earlier, though this also
seems to be a warning.
Did you install paramiko from RPM?
What version of ansible?
Hi Michael,
Paramiko came from yum, ansible was on the v1.0 tag. The issue was due to an invalid MTU setting on a router but I think ansible could provide better feedback than that line. I added the lines
import logging
logging.basicConfig()
to paramiko_ssh.py which led me to the actual paramiko error ‘104 Connection reset’ by peer’ or similar which, in a roundabout way, led me to this http://stackoverflow.com/questions/10285700/curl-error-recv-failure-connection-reset-by-peer-php-curl/10349895#10349895 and hence the MTU setting.
Should paramiko logging be configured by default?
Brent
Depends on how verbose it is, assume it just goes to syslog by default?