Hi, DBRay,

Thank-you for your suggestion; explicitly using this version of net-ssh 
does not appear to solve the problem.   Thank-you for your suggestion, 
though.  If you had any other suggestions I would definitely be interested 
in hearing them.

Dan Sullivan

On Saturday, May 25, 2013 5:33:45 AM UTC-5, dbray wrote:
>
> Dan,
>
> I still have this line in my Gemfile for my older Ree 1.8.7 application
>
> Add it to yours and see if it helps.
>
>  
>   gem 'net-ssh', '2.4.0' #https://github.com/net-ssh/net-ssh/issues/45 Known 
> issue with 2.5.1
>
>  
>
>
> On Sat, May 25, 2013 at 1:06 AM, Lee Hambley <[email protected]<javascript:>
> > wrote:
>
>> Dan,
>>
>> That looks like the same "we think it's Net::SSH" issue - if you can find 
>> a way to crank the reporting level on Net::SSH to "Debug" you see a lot 
>> more information (down to bytes on the stream) and might be able to better 
>> diagnose it.
>>
>> FWIW, 1.8.7 is now officially unsupported by Ruby, and as such 
>> unsupported by us, although the README still says otherwise.
>>
>> - Lee
>>
>> Lee Hambley
>> --
>> http://lee.hambley.name/
>> +49 (0) 170 298 5667
>>  
>>
>> On 25 May 2013 05:01, Dan Sullivan <[email protected] <javascript:>>wrote:
>>
>>> Hi,
>>>
>>> I am having a weird error during a deployment using capistrano 2.x.    I 
>>> am unsure whether or not this is directly related to net-ssh (as suggested 
>>> below), or by Capistrano itself (the occurs when executing a Capistrano 
>>> task).  First and foremost, I want to say that I am fairly confident that 
>>> this was working before; I'm guessing that this error has something to do 
>>> with a newer version of net-ssh and or Capistrano, however this has yet to 
>>> be proven.
>>>
>>> The full stack trace of my error is here:
>>>
>>> http://pastie.org/7956002
>>>
>>> What is particularly unusual to me is that if I run a single command in 
>>> the task, the command (i.e. create a directory), the task runs fine.  As 
>>> soon as I run a second command in the same task, the deployment script 
>>> bombs out with the stack trace above, even if it is the exact same command 
>>> run twice in a row in the same task (as defined in the pastie below).
>>>
>>> I've stripped down my deploy.rb to include a very minimal amount of code 
>>> to illustrate the problem.  The past of this code is here.
>>>
>>> http://pastie.org/7955994
>>>
>>> I am running ruby 1.8.7 (2012-10-12 patchlevel 371) [x86_64-linux] and 
>>> Capistrano v2.15.4.
>>>
>>> In addition to this, I am running ruby RVM ruby-1.8.7-p371.  Finally, my 
>>> bundle list is below:
>>>
>>> I would really appreciate any insight that somebody could provide for me 
>>> in resolving this issue.  Thank-you so much for your time and attention in 
>>> helping me look at this problem.
>>>
>>> Dan Sullivan
>>>
>>> --[dps@neve]-[/tmp/asap/asap]--
>>> > bundle list
>>> Gems included by the bundle:
>>>   * actionmailer (2.3.14)
>>>   * actionpack (2.3.14)
>>>   * activerecord (2.3.14)
>>>   * activeresource (2.3.14)
>>>   * activesupport (2.3.14)
>>>   * builder (3.2.0)
>>>   * bundler (1.3.5)
>>>   * capistrano (2.15.4)
>>>   * configatron (2.6.3)
>>>   * declarative_authorization (0.4.1)
>>>   * fastercsv (1.5.3)
>>>   * haml (3.0.4)
>>>   * highline (1.6.19)
>>>   * hoptoad_notifier (2.4.7)
>>>   * liquid (2.0.0)
>>>   * memcache-client (1.8.3)
>>>   * mysql (2.9.1)
>>>   * net-scp (1.1.1)
>>>   * net-sftp (2.1.2)
>>>   * net-ssh (2.6.7)
>>>   * net-ssh-gateway (1.2.0)
>>>   * newrelic_rpm (2.13.4)
>>>   * nokogiri (1.4.1)
>>>   * paperclip (2.3.1.1)
>>>   * pdfkit (0.5.2)
>>>   * prawn (0.8.4)
>>>   * prawn-core (0.8.4)
>>>   * prawn-layout (0.8.4)
>>>   * prawn-security (0.8.4)
>>>   * preferences (0.4.2)
>>>   * rack (1.1.6)
>>>   * rails (2.3.14)
>>>   * rake (0.8.7)
>>>   * ruby_parser (2.0.6)
>>>   * sanitize (1.2.1)
>>>   * searchlogic (2.5.14)
>>>   * sexp_processor (3.2.0)
>>>   * slim_scrooge (1.0.11)
>>>   * uuidtools (2.1.1)
>>>   * version_bumper (0.3.0)
>>>   * will_paginate (2.3.12)
>>>   * yamler (0.1.0)
>>> --[dps@neve]-[/tmp/asap/asap]--
>>> > 
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>  -- 
>>> -- 
>>> * You received this message because you are subscribed to the Google 
>>> Groups "Capistrano" group.
>>> * To post to this group, send email to 
>>> [email protected]<javascript:>
>>> * To unsubscribe from this group, send email to 
>>> [email protected] <javascript:> For more options, visit 
>>> this group at http://groups.google.com/group/capistrano?hl=en
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Capistrano" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected] <javascript:>.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>
>>  -- 
>> -- 
>> * You received this message because you are subscribed to the Google 
>> Groups "Capistrano" group.
>> * To post to this group, send email to [email protected]<javascript:>
>> * To unsubscribe from this group, send email to 
>> [email protected] <javascript:> For more options, visit 
>> this group at http://groups.google.com/group/capistrano?hl=en
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Capistrano" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
-- 
* You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
* To post to this group, send email to [email protected]
* To unsubscribe from this group, send email to 
[email protected] For more options, visit this group at 
http://groups.google.com/group/capistrano?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to