Re: [Fab-user] Getting fatal error 'No handlers could be found for logger "paramiko.transport"'

[Jeff Forcier]

Glad you figured it out, Hakan! Now that you mention it I do think this has 
come up before -- I'll write a ticket on our tracker so that it's more easily 
discoverable, and as Christian mentions, so we can try and fix the root of the 
problem.

When I looked last night, it seemed all at the Paramiko level, which implies to 
me that their logging code has bugs in it. We certainly aren't doing anything 
with the logging module ourselves.

I've just made two tickets from this thread:

    http://code.fabfile.org/issues/show/51 - Paramiko logger message
    http://code.fabfile.org/issues/show/52 - full stack trace option

Best,
Jeff

On Fri, Aug 14, 2009 at 01:18:30PM +0200, Christian Vest Hansen wrote:
> Good you got it solved. The 'No handlers could be found for logger
> "paramiko.transport"' message doesn't look terribly telling about the
> cause, but I suppose it is caused by paramiko trying to log the real
> cause of the error (that env.user should be a simple string) and
> failing because no log handler is defined. I remember seeing a message
> like that before, and subsequently trying to programatically configure
> the logging but I couldn't figure it out and gave up. Perhaps I forgot
> to read the documentation:
> http://docs.python.org/library/logging.html#configuring-logging - it
> looks pretty easy from that example.
> 
> On Fri, Aug 14, 2009 at 11:25 AM, H??kan Waara<address@hidden> wrote:
> > A-ha! The error was this:
> >
> > env.user = ['foobar']
> >
> > env.user is not an array like hosts, as I thought it was!
> >
> > This solves the problem. Sorry for the noise!
> >
> > BTW, I agree that stacktrace for the errors would be nice, that would be a
> > start for where to look even for stupid user-errors like this one.
> >
> > Thanks,
> > H??kan
> >
> > 14 aug 2009 kl. 11.17 skrev H??kan Waara:
> >
> >> I still get the same error with Paramiko 1.7.4. Hmm, I don't know how to
> >> debug more. I see no verbosity setting, and looking at the source haven't
> >> helped so far.
> >>
> >> /H??kan
> >>
> >> 14 aug 2009 kl. 11.00 skrev H??kan Waara:
> >>
> >>> I'm on the latest "canonical" git, i.e. the URL that is mirrored from
> >>> fabfile.org. Specifically this revision:
> >>> git://fabfile.org/address@hidden
> >>>
> >>> I'll try with Paramiko 1.7.4 next. I've attached my fabfile.py to this
> >>> mail (with user and hosts scrubbed out, hope you don't mind). The command
> >>> that fails is fab test deploy.
> >>>
> >>> Let me know if I can provide you with more details!
> >>>
> >>> /H??kan
> >>>
> >>> 14 aug 2009 kl. 05.03 skrev Jeff Forcier:
> >>>
> >>>> Hi again,
> >>>>
> >>>> I've just set up a virtualenv with Paramiko 1.7.5 and I can't recreate
> >>>> this, even with the same call you're specifying (cd <dir> ; hg up).
> >>>>
> >>>> D
> >>>
> >>> <fabfile.py>
> >>>>
> >>>> oes this occur for you every time and always on that same line? Is
> >>>> this the first line in your fabfile, i.e. do other run() calls work
> >>>> fine but this one blows up? Etc. Need more info :)
> >>>>
> >>>> It seems like a pretty odd error to get, given the one or two spots in
> >>>> Paramiko where it could be showing up.
> >>>>
> >>>> I've been wanting to make it possible to get a full stack trace out of
> >>>> errors instead of just printing the single text message of the
> >>>> exception. If we can't nail this some other way I may add that option
> >>>> on master and ask you to update and test with it, to give us a
> >>>> slightly clearer picture of what is breaking.
> >>>>
> >>>> -Jeff
> >>>>
> >>>> On Thu, Aug 13, 2009 at 7:57 PM, Jeff Forcier<address@hidden>
> >>>> wrote:
> >>>>>
> >>>>> Hi Hakan,
> >>>>>
> >>>>> Any chance you can try downgrading Paramiko to 1.7.4? I've not used
> >>>>> 1.7.5 yet and I'm not sure if many others have, and it could be a bug
> >>>>> introduced by that new version.
> >>>>>
> >>>>> When you say you're on the latest git, I assume you mean you're on the
> >>>>> master branch?
> >>>>>
> >>>>> -Jeff
> >>>>>
> >>>>> On Thu, Aug 13, 2009 at 7:47 PM, H??kan Waara<address@hidden> wrote:
> >>>>>>
> >>>>>> Hi all,
> >>>>>>
> >>>>>> I'm getting a fatal error which aborts my fabfile:
> >>>>>>
> >>>>>> from my fabfile.py:
> >>>>>> ...
> >>>>>> ??# update the mercurial repository remotely
> >>>>>> ??print run("cd %(repo_path)s; hg up" % env)
> >>>>>> ...
> >>>>>>
> >>>>>> This shows up as this (and fails):
> >>>>>>
> >>>>>> [foo.bar] run: cd foobar; hg up
> >>>>>> No handlers could be found for logger "paramiko.transport"
> >>>>>>
> >>>>>> Any ideas? I'm running from the latest git trunk code, and have
> >>>>>> paramiko
> >>>>>> 1.7.5 installed on python 2.6
> >>>>>>
> >>>>>> /H??kan
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Fab-user mailing list
> >>>>>> address@hidden
> >>>>>> http://lists.nongnu.org/mailman/listinfo/fab-user
> >>>>>>
> >>>>>
> >>>
> >>
> >
> >
> >
> > _______________________________________________
> > Fab-user mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/fab-user
> >
> 
> 
> 
> -- 
> Venlig hilsen / Kind regards,
> Christian Vest Hansen.