Re: [Fab-user] Fabric 1.4 hangs on run('git fetch && git fetch --tags')

[Ivan Sergeyenko]

Sure, here you go:

<master>address@hidden:~/work/clients/X/deploy$ fab test
[108.166.71.99] Executing task 'test'
[108.166.71.99] run: git fetch && git fetch --tags
DEBUG:ssh.transport:starting thread (client mode): 0x19f1e90L
INFO:ssh.transport:Connected (version 2.0, client OpenSSH_5.8p1)
DEBUG:ssh.transport:kex algos:['ecdh-sha2-nistp256',
'ecdh-sha2-nistp384', 'ecdh-sha2-nistp521',
'diffie-hellman-group-exchange-sha256',
'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1',
'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client
encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256',
'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc',
'aes192-cbc', 'aes256-cbc', 'arcfour', 'address@hidden']
server encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr',
'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc',
'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfour',
'address@hidden'] client mac:['hmac-md5', 'hmac-sha1',
'address@hidden', 'hmac-ripemd160', 'address@hidden',
'hmac-sha1-96', 'hmac-md5-96'] server mac:['hmac-md5', 'hmac-sha1',
'address@hidden', 'hmac-ripemd160', 'address@hidden',
'hmac-sha1-96', 'hmac-md5-96'] client compress:['none',
'address@hidden'] server compress:['none', 'address@hidden']
client lang:[''] server lang:[''] kex follows?False
DEBUG:ssh.transport:Ciphers agreed: local=aes128-ctr, remote=aes128-ctr
DEBUG:ssh.transport:using kex diffie-hellman-group1-sha1; server key
type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local
hmac-sha1, remote hmac-sha1; compression: local none, remote none
DEBUG:ssh.transport:Switch to new keys ...
DEBUG:ssh.transport:Trying SSH agent key eedd2236a603e0a26be3feee1fdf07db
DEBUG:ssh.transport:userauth is OK
INFO:ssh.transport:Authentication (publickey) successful!
DEBUG:ssh.transport:[chan 1] Max packet in: 34816 bytes
DEBUG:ssh.transport:[chan 1] Max packet out: 32768 bytes
INFO:ssh.transport:Secsh channel 1 opened.
DEBUG:ssh.transport:[chan 1] Sesch channel 1 request ok
DEBUG:ssh.transport:[chan 1] Sesch channel 1 request ok
DEBUG:ssh.transport:Incoming forward agent connection
DEBUG:ssh.transport:[chan 2] Max packet in: 34816 bytes
DEBUG:ssh.transport:[chan 2] Max packet out: 16384 bytes
INFO:ssh.transport:Secsh channel 2 (address@hidden) opened.
DEBUG:ssh.transport:[chan 2] EOF received (2)
DEBUG:ssh.transport:Incoming forward agent connection
DEBUG:ssh.transport:[chan 3] Max packet in: 34816 bytes
DEBUG:ssh.transport:[chan 3] Max packet out: 16384 bytes
INFO:ssh.transport:Secsh channel 3 (address@hidden) opened.
DEBUG:ssh.transport:[chan 2] EOF sent (2)


On Thu, Feb 23, 2012 at 11:54 PM, Jeff Forcier <address@hidden> wrote:
> On Thu, Feb 23, 2012 at 8:25 PM, Ivan Sergeyenko <address@hidden> wrote:
>> Hi Jeff,
>>
>> Yes, I am using agent forwarding and SSH remote. Switching to HTTPS
>> remote fixed the issue. Disabling forwarding and using local public
>> key with SSH remote works as well.
>
> OK, thanks, so it may be a similar problem to what the other user experienced.
>
> If you have the time, could you enable the stdlib logging module in
> your fabfile, at level DEBUG, and send me a copy of the output from
> when you run it with forwarding on + SSH remote (i.e. the problem
> scenario)? It should spit out a bunch of 'ssh.<whatevs>' log lines.
>
> Best,
> Jeff
>
>>
>> Thanks,
>> Ivan
>>
>> On Thu, Feb 23, 2012 at 10:15 PM, Jeff Forcier <address@hidden> wrote:
>>> Hi Ivan
>>>
>>> On Thu, Feb 23, 2012 at 3:57 PM, Ivan Sergeyenko <address@hidden> wrote:
>>>
>>>> As far as I can tell, both commands are executed, but Fabric never
>>>> gets notified that they're done. Splitting the command into two "run"
>>>> statements fixes the issue:
>>>
>>>> I have tried this on multiple servers with different git repos, always
>>>> getting the same result. Needless to say, running the same command
>>>> manually on the server works fine.
>>>
>>> Do you have the new agent forwarding behavior enabled, and is the git
>>> remote in question SSH-based (vs https:// or git://)? I've heard one
>>> other report of odd/buggy behavior when running Git remotely + using
>>> agent forwarding, though that case was an SSHException being raised,
>>> not a hang, IIRC.
>>>
>>> If you're using agent forwarding and/or are using an SSH remote, you
>>> could try disabling it and using git:// or https:// for the git repo's
>>> remote URL, and see if the combo command still breaks. That might at
>>> least help narrow down what the problem is.
>>>
>>> Best,
>>> Jeff
>>>
>>> --
>>> Jeff Forcier
>>> Unix sysadmin; Python/Ruby engineer
>>> http://bitprophet.org
>
>
>
> --
> Jeff Forcier
> Unix sysadmin; Python/Ruby engineer
> http://bitprophet.org