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,
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
We had this same issue and we narrowed it down to paramiko 1.7.5
We were getting exceptions like:
Traceback (most recent call last):
File /home/christian/.virtualenvs/pstat_dev/src/fabric/fabric/main.py,
line 454, in main
commands[name](*args, **kwargs)
File
That's fantastic news! At least I can get going while we try to work
out what is going on.
Thanks,
Ted C.
On Aug 14, 2009, at 9:06 AM, Wes Winham wrote:
We had this same issue and we narrowed it down to paramiko 1.7.5
We were getting exceptions like:
Traceback (most recent call last):
Hello everybody,
what would be the best practice to integrate or include a separate .py
file that lists my server groups.
(I would like to reuse my functions that are stored in fabfile, but
also make it consume definitions of groups defining env.hosts that are
regenerated quite often).
Hi Thomas,
Right now there's no specific best practices -- Fabric tries hard to be just
Python, meaning that you can do anything you might normally do with Python
code. So if you have some code that somehow generates your host list, you could
stick that in e.g. get_hosts.py, then in your fabfile
Thanks for confirming this, both of you. I also note that Pat
McNerthney just (as in 10 minutes ago) actually investigated this and
put a nice, detailed comment on Robey's Paramiko Github page outlining
what's going on:
I was just going to send a message here about this, but you beat me to it!
I just today starting using Fabric again and bumped into this very
issue. This thread helped a lot in pointing me to the right direction.
I submitted a patch that resolves this problem in 1.7.5 here:
Hi folks,
First, I'm going to be largely AFK for the next three to four days
(vacation) so please don't be dispirited if I am even less responsive
than usual ;) I'll do my best to catch up when I return or if I find
downtime while away.
Second, I'm hoping to do a documentation sprint (tutorial
