Btw, are you on Gentoo? I saw this error on my Gentoo boxes. There is a funky RUBYOPT option set in /etc somewhere. But I am unsure of how it applies or how to get around it. I think the previous post is pointing the way though.
On Tue, Mar 23, 2010 at 5:52 AM, Lee Hambley <[email protected]> wrote: > Irene, > > Looks like a change in behavior of PTY versus TTY on your machine, under > normal circumstances (read: an ssh login) you'll get a TTY (thus the name of > the PuTTY software for Windows) - and depending on your Capistrano > configuration, you will get one or the other. > > Essentially there's very little documentation around on the subject, and > it's a bit of black-box, as it also is different on many distributions. > > As a rule, to emulate the way Capistano behaves, you can pass directly to > ssh instructions like this: > > ssh [email protected] 'which ruby' > > Note they are single quotes, not back-ticks! > > In a nutshell, you'll likely find the same behavior as Capistrano is > displaying through the "non-login shell" that SSH gives you above. In a word > - your server is probably not evaluating your environmental configuration, > bash profile/login/etc. > > -- Lee Hambley > > Twitter: @leehambley | @capistranorb > > Please consider the environment before printing this email > Join the campaign at http://thinkBeforePrinting.org > > > > On 23 March 2010 00:13, Iros <[email protected]> wrote: >> >> Hi All, >> >> This will seem like a ridiculous question but we are rather baffled >> ourselves. We have two identical machines (vm images that are clones) >> one of which has recently been upgraded by our "trusty" admin to >> OpenSSH 5.4p1. As of the upgrade, we are no longer able to cap deploy >> to that machine (while still being able to deploy to the other >> image.) >> >> The issue we are seeing is pretty far down the stack, in that we are >> able to ssh in, copy our tar.gz and so on. The problem occurs when we >> try to run one of our ruby scripts that does a bit of set up for us. >> We get a >> "no such file to load -- rubygems (LoadError)" as our deploy user. If >> we ssh into the machine as that user, we can require 'rubygems' in irb >> just fine, it only happens as part of our cap script. >> >> Any ideas guys? This is pretty strange. >> Thanks, >> -- Irene >> >> -- >> * 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 >> >> To unsubscribe from this group, send email to >> capistrano+unsubscribegooglegroups.com or reply to this email with the words >> "REMOVE ME" as the subject. > > -- > * 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 > > To unsubscribe from this group, send email to > capistrano+unsubscribegooglegroups.com or reply to this email with the words > "REMOVE ME" as the subject. > -- * 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 To unsubscribe from this group, send email to capistrano+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
