I'd love some suggestions for how to easily duplicate the problem,
actually. I wasn't able to duplicate the problem on that account after
all--it was just uploading really slowly. And it was uploading really
slowly via the OpenSSH sftp utility, too, so it wasn't just the
Net::SFTP or Net::SSH libs.

- Jamis

On 7/20/07, Andrew Beacock <[EMAIL PROTECTED]> wrote:
>
> Thanks Jamis for the update, if you need any help testing out patches
> or alternative suggestions please let me know - I'd be happy to help
> get to the bottom of this one :)
>
> Andy
>
> --
> Andrew Beacock
> blog: http://blog.andrewbeacock.com
>
>
> On Jul 19, 2:48 pm, "Jamis Buck" <[EMAIL PROTECTED]> wrote:
> > Andy,
> >
> > I'm investigating even as we speak. I was set up with an account that
> > exhibited the problem, and I was finally able to duplicate the problem
> > there, which has helped. I'll post more as soon as I have more info.
> >
> > - Jamis
> >
> > On 7/19/07, Andrew Beacock <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > Jamis,
> >
> > > Have you been able to investigate this further?  I'm still getting the
> > > issue (even when running with just one role).  "require 'fastthread"
> > > seems to help but not solve the problem.
> >
> > > Andy
> >
> > > --
> > > Andrew Beacock
> > > blog:http://blog.andrewbeacock.com
> >
> > > On Jul 11, 7:55 pm, "Jamis Buck" <[EMAIL PROTECTED]> wrote:
> > > > That would help immensely. As it is, the only error I can duplicate
> > > > consistently is a "corrupted mac" error when performing two or more
> > > > simultaneous large uploads via a gateway...which is not the same error
> > > > others are seeing.
> >
> > > > - Jamis
> >
> > > > On 7/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > > > > jamis, if it would help.
> > > > > I could see if my hosting provider can get you access to an instance 
> > > > > on
> > > > > the machine.
> >
> > > > > On 7/11/07, Jamis Buck <[EMAIL PROTECTED]> wrote:
> >
> > > > > > Note that 100% CPU consumption is a known issue with Net::SFTP, and 
> > > > > > is
> > > > > > not necessarily related to the upload hanging. Even when everything
> > > > > > works correctly, you will still see huge CPU usage by Net::SFTP.
> >
> > > > > > - Jamis
> >
> > > > > > On 7/11/07, AndrewBeacock<[EMAIL PROTECTED]> wrote:
> >
> > > > > > > Just a little more information:
> > > > > > > If I comment out my :web and :db targets (leaving just :app) then 
> > > > > > > 9
> > > > > > > out of 10 times the deploy works correctly.
> >
> > > > > > > As soon as I add my :db target back in (a different hostname) it 
> > > > > > > hangs
> > > > > > > in the same place as before.
> >
> > > > > > > Andy.
> > > > > > > --
> > > > > > > AndrewBeacock
> > > > > > > Blog:http://blog.andrewbeacock.com
> >
> > > > > > > On Jul 11, 10:25 am, AndrewBeacock< [EMAIL PROTECTED]> wrote:
> > > > > > > > Spoke too soon :(
> >
> > > > > > > > It worked once (after I added the require line) but not again 
> > > > > > > > still
> > > > > > > > hangs at the same place ("** uploading data to ...")  and I 
> > > > > > > > thought I
> > > > > > > > was using 1.8.6 but obviously not!
> >
> > > > > > > > I'm using:
> >
> > > > > > > > Ubuntu 6.10 (lsb_release -r -> 6.10)
> > > > > > > > Kernel 2.6.17 (uname -a -> Linux 2.6.17-11-386 #2 Fri May 18 
> > > > > > > > 23:37:00
> > > > > > > > UTC 2007 i686 GNU/Linux)
> > > > > > > > Ruby 1.8.4 (ruby -v -> ruby 1.8.4 (2005-12-24) [i486-linux])
> > > > > > > > capistrano (1.99.3)
> > > > > > > > fastthread (1.0)
> > > > > > > > highline (1.2.9)
> > > > > > > > net-sftp ( 1.1.0)
> > > > > > > > net-ssh (1.1.2)
> >
> > > > > > > > I have a different host listed for my :db than my :app (the 
> > > > > > > > :web is
> > > > > > > > the same as the :app).
> >
> > > > > > > > Andy.
> > > > > > > > --
> > > > > > > > AndrewBeacock
> > > > > > > > Blog:http://blog.andrewbeacock.com
> >
> > > > > > > > On Jul 11, 10:11 am, AndrewBeacock<[EMAIL PROTECTED]> wrote:
> >
> > > > > > > > > Ezra,
> > > > > > > > > Thank you so much!  I've only started with Capistrano this 
> > > > > > > > > morning
> > > > > > > > > (gem'ing v2) and had this very issue (I'm using Ruby 1.8.6).  
> > > > > > > > > I've
> > > > > > > > > just added the require 'fastthread' to the top of my Capfile 
> > > > > > > > > and now
> > > > > > > > > it all works fine to two different hosts.
> >
> > > > > > > > > Andy.
> > > > > > > > > --
> > > > > > > > > Blog:http://blog.andrewbeacock.com
> >
> > > > > > > > > On Jul 11, 12:32 am, Ezra Zygmuntowicz <[EMAIL PROTECTED]> 
> > > > > > > > > wrote:
> >
> > > > > > > > > >         What version of RUby itself are all of you 
> > > > > > > > > > experiencing
> > > > > this problem
> > > > > > > > > > running? Is it perhaps ruby 1.8.6? I've been doing file 
> > > > > > > > > > transfers
> > > > > > > > > > with cap here of up to 25Mb without ever seeing this issue 
> > > > > > > > > > no
> > > > > matter
> > > > > > > > > > what i call before or after the put command. THis was with 
> > > > > > > > > > ruby
> > > > > 1.8.5
> >
> > > > > > > > > >         But I just tried it with ruby 1.8.6 and was able to 
> > > > > > > > > > get
> > > > > the same
> > > > > > > > > > deadlocking error.  Ruby 1.8.6 has a bug in the threading 
> > > > > > > > > > code
> > > > > that
> > > > > > > > > > causes deadlocks sometimes.
> >
> > > > > > > > > >         Can those of you having this issue please install 
> > > > > > > > > > the
> > > > > fastthread gem
> > > > > > > > > > and add require 'fastthread' to the top of your recipe 
> > > > > > > > > > files and
> > > > > > > > > > report back please?
> >
> > > > > > > > > > Thanks
> > > > > > > > > > -- Ezra Zygmuntowicz
> > > > > > > > > > -- Lead Rails Evangelist
> > > > > > > > > > -- [EMAIL PROTECTED]
> > > > > > > > > > -- Engine Yard, Serious Rails Hosting
> > > > > > > > > > -- (866) 518-YARD (9273)
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to