I met same problem like this, but when adding ssh_options[:debug] = :verbose
in deploy.rb, i got: invalid option(s) to Net::SSH::Transport::Session: [:debug] anything wrong? - crax On 3月5日, 上午5时07分, Jamis Buck <[EMAIL PROTECTED]> wrote: > You can try putting the following in your deploy.rb: > > ssh_options[:debug] = :verbose > > Running cap will then spew out an ENORMOUS amount of Net::SSH > debugging info, to your console. If you'll save that to a file and > email it to me directly, I can look over it and see if there is > anything fishy going on. > > Be sure to edit the output before sending it to me, to remove > anything sensitive like passwords and such, since they'll all show up > in clear text in the debugging output. > > - Jamis > > On Mar 4, 2007, at 1:51 PM, Jordan McKible wrote: > > > > > I built it myself. > > > $ ruby -v > > ruby 1.8.5 (2006-12-25 patchlevel 12) [i686-darwin8.8.2] > > > Same version is on remote, if that matters. > > > On Mar 4, 3:47 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > >> What version of Ruby are you running locally? Is it the Ruby that > >> comes preinstalled with OS X, or did you build it yourself? > > >> - Jamis > > >> On Mar 4, 2007, at 1:41 PM, Jordan McKible wrote: > > >>> I've been able to run the setup task a few times successfully. > >>> deploy > >>> is still hanging on random commands. I've seen cp, rm, and ls > >>> commands all get defunct on the remote server. I can't seem to > >>> narrow > >>> the problem down to one place. > > >>> On Mar 4, 2:41 pm, "Jordan McKible" <[EMAIL PROTECTED]> wrote: > >>>> Local is OS X 10.4.8 > >>>> Remote is Debian 3.1 > > >>>> The old machine was Ubuntu 6.06.1 and it was running without a > >>>> hitch. > > >>>> I've also got Capistrano 1.4.1 > > >>>> On Mar 4, 2:36 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > > >>>>> What is the OS, both local and remote? > > >>>>> - Jamis > > >>>>> On Mar 4, 2007, at 12:26 PM, Jordan McKible wrote: > > >>>>>> I'm trying to get cap setup on a new machine and I'm having some > >>>>>> problems. Whenever I run a task, my local machine hangs on > >>>>>> executing > >>>>>> the command. For example: > > >>>>>> $ cap setup > >>>>>> * executing task setup > >>>>>> * executing "umask 02 &&\n mkdir -p /var/rails /var/rails/ > >>>>>> releases /var/rails/shared /var/rails/shared/system &&\n > >>>>>> mkdir -p / > >>>>>> var/rails/shared/log &&\n mkdir -p /var/rails/shared/pids" > >>>>>> servers: ["xxx.xxx.xxx.xxx"] > >>>>>> [xxx.xxx.xxx.xxx] executing command > > >>>>>> And nothing ever happens. I believe it's waiting for a reply > >>>>>> from the > >>>>>> server. Here's what the server shows is happening: > > >>>>>> ~$ ps auxf | grep jmckible > >>>>>> jmckible 21280 0.0 0.1 3728 1332 ? S 14:18 0:00 > >>>>>> sshd: > >>>>>> [EMAIL PROTECTED]/1 > >>>>>> jmckible 21281 0.0 0.0 0 0 ? Zs 14:18 > >>>>>> 0:00 \_ > >>>>>> [bash] <defunct>defunct> > > >>>>>> I believe that defunct process is the capistrano task. > >>>>>> However, it > >>>>>> seems it's become zombified so the task on my local machine is > >>>>>> hanging. > > >>>>>> Has anyone seen something like this before? > > >>>>>> Jordan > > >>>>> smime.p7s > >>>>> 3KDownload > > >> smime.p7s > >> 3KDownload > > > > > > > smime.p7s > 3K下载 --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
