Fabric hanging on some remote commands (was Re: [Fab-user] Beta 1 out)

[Jeff Forcier]

Hi Niklas,

First, as you may have seen, I tweaked the "missing output" issue
today. For some reason I had lumped your issue in with that problem,
but after fixing it I doubt it impacts your situation with Tomcat.
Even so, if you can yank the latest master or 0.9 and give it a shot,
that would help confirm my assumption :)

Second, my reply:

2009/7/25 Niklas Lindström <address@hidden>:

> You are indeed correct, revision
> 7e7fd8a6bd75cc46c857b77954e297d2bb685c93 (re-)introduced this bug.
>
> I took a look in "/etc/init.d/tomcat6" (on Ubuntu). The part causing
> the stall is when starting the daemon (using "/usr/bin/jsvc"). It
> doesn't seem to be related to the duration of the restart. (I have not
> been able to reproduce the freeze by restarting apache nor using
> Python Paste:s daemon mode.)

There's two things I'd like you to do if possible:

1. See how /usr/bin/jsvc behaves when invoked normally and via the
init script. What's its return/exit code? Does it daemonize properly?
Is it forking into the background instead of daemonizing or something
silly like that? Etc.

This is all shooting wild -- I doubt this problem is actually jsvc's
fault, and even if it is we can probably still route around it -- but
I just want to know what we're dealing with.

2. Throw some debug/print statements into fabric/operations.py, inside
run() (i.e the area diffed in "git show 7e7fd8a") to see whether the
hang is Python waiting for the outputter threads to join up, or if
it's in the waiting for the channel to close, or if it's something
beyond that.

Best,
Jeff