Re: [Fab-user] Setting the log level causes fabric to complain with 'No handlers could be found for logger "ssh.transport"'

[Jeff Forcier]

Hi Daniel,

On Thu, Mar 29, 2012 at 7:19 AM, Daniel Gonzalez <address@hidden> wrote:

> I would like to get rid of this annoying error message: "No handlers could
> be found for logger "ssh.transport""
> The problem happens when setting the log level (setLevel).

This is an issue with one of our dependencies, ssh/paramiko:

    https://github.com/fabric/fabric/issues/51

I believe you can force ssh's log entries to get logged instead of
warn, by running logging.basicConfig(), which (my logging-fu is weak
right now) probably takes care of setting up a default handler for all
streams.

That'll send ssh's log stuff to the same place your INFO is going; if
you want to make it go elsewhere, read up on the stdlib's logging
module -- there should be a way to tell it to send "ssh.transport"
events elsewhere.

Best,
Jeff



-- 
Jeff Forcier
Unix sysadmin; Python/Ruby engineer
http://bitprophet.org