# Paramiko error **URL:** \ **Category:** Ansible Project\ **Tags:** ansible-project\ **Created:** [March 18, 2013, 1:32pm UTC](https://forum.ansible.com/t/paramiko-error/12522 "2013-03-18T13:32:23Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\ **Post date:** [March 18, 2013, 1:32pm UTC](https://forum.ansible.com/t/paramiko-error/12522/1 "2013-03-18T13:32:23Z")
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? ---
**Author:** ![Brent\_Douglas](https://avatars.discourse-cdn.com/v4/letter/b/c68b51/32.png) [@Brent\_Douglas](https://forum.ansible.com/u/Brent_Douglas)\ **Post date:** [March 18, 2013, 10:38pm UTC](https://forum.ansible.com/t/paramiko-error/12522/2 "2013-03-18T22:38:44Z")
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](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 ---
**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\ **Post date:** [March 19, 2013, 2:07am UTC](https://forum.ansible.com/t/paramiko-error/12522/3 "2013-03-19T02:07:39Z")
Depends on how verbose it is, assume it just goes to syslog by default?