Re: [Fab-user] Getting fatal error 'No handlers could be found for logger paramiko.transport'
I'm on the latest canonical git, i.e. the URL that is mirrored from fabfile.org. Specifically this revision: git://fabfile.org/ fabric@71a01cd960b50b2ce5ffd2faa6fcf3b7b98bb60b 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# encoding: utf-8 from fabric.api import local, run, env env.hosts = ['foobar.bar'] env.host = env.hosts[0] # hack to access this host easily env.user = ['foobar'] def test(): env.repo_path = foobar_test env.wsgi_path = /var/www/wsgi-scripts/foobar_test.wsgi def production(): env.repo_path = foobar env.wsgi_path = /var/www/wsgi-scripts/foobar.wsgi def deploy(): # push the code print local(hg push ssh://%(host)s/%(repo_path)s % env) # update it remotely print run(cd %(repo_path)s; hg up % env) # make apache reload the app to pick up changes print run(touch %(wsgi_path)s % env) 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 Forcierj...@bitprophet.org 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 Waarahwa...@gmail.com 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 Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user ___ Fab-user mailing list Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user
Re: [Fab-user] Getting fatal error 'No handlers could be found for logger paramiko.transport'
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 Waarahwa...@gmail.com 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/fabric@71a01cd960b50b2ce5ffd2faa6fcf3b7b98bb60b 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 Forcierj...@bitprophet.org 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 Waarahwa...@gmail.com 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 Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user ___ Fab-user mailing list Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user -- Venlig hilsen / Kind regards, Christian Vest Hansen. ___ Fab-user mailing list Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user
Re: [Fab-user] Getting fatal error 'No handlers could be found for logger paramiko.transport'
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 Waarahwa...@gmail.com 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 Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user ___ Fab-user mailing list Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user
Re: [Fab-user] Getting fatal error 'No handlers could be found for logger paramiko.transport'
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). Does 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 Forcierj...@bitprophet.org 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 Waarahwa...@gmail.com 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 Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user ___ Fab-user mailing list Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user
