Handle Paramiko-level "logger" issues

Description

This has come up at least twice now: a user sets env.user to a list instead of a string by mistake, and instead of an actual useful error, we get a funky No handlers could be found for logger "paramiko.transport" message.

Quick research implies that this is a Paramiko level bug, as we don’t use the logger module ourselves and that particular logger name is used in Paramiko itself. However, if it is, it’s not caught in their test suite.

Attack plan:

• Look at Paramiko’s mailing list or bug tracker and see if this is a known issue
• Attempt to troubleshoot ourselves if not
• Once solved, inform upstream
• Failing all else, deal with this specific problem at our level: issue our own useful alert when user is set to a list value.

---

Originally submitted by Jeff Forcier (bitprophet) on 2009-08-14 at 09:58am EDT

Relations

• Related to #52: Allow display of full stack trace on error
• Related to #57: improved logging

[fgimian]

I think it might be your order. Here’s the start of my fabfile.py 😄

import logging

from fabric.api import env, task, abort
from fabric.exceptions import CommandTimeout, NetworkError
from fabric.state import output

# Workaround for: No handlers could be found for logger "paramiko.transport"
# (see https://github.com/fabric/fabric/issues/51#issuecomment-96341022)
logging.basicConfig()
paramiko_logger = logging.getLogger("paramiko.transport")
paramiko_logger.disabled = True

Cheers fotis

[fgimian]

Same problem here with the latest of everything, it seems to happen when the connection to the host hangs 😄

Here’s how I worked around it:

import logging

logging.basicConfig()
paramiko_logger = logging.getLogger("paramiko.transport")
paramiko_logger.disabled = True

This was added to the top of my fabfile.py file.