no logger registered for paramiko

Bug #494345 reported by Martin Pool on 2009-12-09
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Medium
Martin Pool

Bug Description

Paramiko sends out messages through the Python logging module. There have been various cases (eg bug 58060) where you got a "no handlers could be found for logger 'bzr.paramiko''". Post merge of https://code.edge.launchpad.net/~mbp/bzr/remove-logging/+merge/14942 so that bzr itself does not use logging, this may be more of a problem. We should send paramiko messages to stderr and the bzr trace file.

Martin Pool (mbp) wrote :

barry hit this in https://answers.edge.launchpad.net/bzr/+question/42886 and there is some diagnosis there

John A Meinel (jameinel) wrote :

Actually, he hit bug #503886, for which I wrote up a patch. (Which is probably a dupe, given that the bug has been around for a long time.) Which might actually be fixed by this bug :). (If we no longer use logging for our own warnings, then _open_bzr_log can use warning() safely, even though paramiko will then fail later because it can't use 'bzr.paramiko'.)

However, we should be able to enable some sort of logging handler once we actually set up paramiko. We already tell paramiko to use "bzr.paramiko" as its logger handle.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers