Sounds like it was trying to connect to a server called "1". You probably want normal cap variables, like:
set :javarole, 1 Or, if it's never used outside that block, simply: javarole = 1 On Mon, Apr 21, 2008 at 1:11 PM, rAge <[EMAIL PROTECTED]> wrote: > > Red Hat Enterprise Linux Server release 5.1 (Tikanga) > ruby 1.8.5 (2006-08-25) [i386-linux] > > My mistake, jumped to conclusions there. I removed a whole block of > puts but within that block was the following command: > role :javarole, "1" > > ^This was truly causing the "Errno::EINVAL: Invalid argument - > connect(2)) " error. Guess I shouldn't try and use roles for other > purposes, I'll create a another variable for this. > > Thanks > > On Apr 21, 11:43 am, Jamis Buck <[EMAIL PROTECTED]> wrote: > > Really? That seems very, very odd. What OS are you using? What version > > of Ruby? I use puts() statements all the time, with no problems. > > > > - Jamis > > > > On Apr 21, 2008, at 11:39 AM, rAge wrote: > > > > > > > > > A few months ago I was having trouble with the following error: > > > > > ** [deploy:update_code] exception while rolling back: > > > Capistrano::ConnectionError, connection failed for: 1 > > > (Errno::EINVAL: > > > Invalid argument - connect(2)) > > > connection failed for: 1 (Errno::EINVAL: Invalid argument - > > > connect(2)) > > > > > I am surprised nobody has seen or written about this error before. > > > Anyway, problem solved! > > > Using "puts" statements within your recipe can affect communication > > > with the destination machine. I switched to print statements for > > > debugging and all my errors disappeared. > > > > > > > > > > smime.p7s > > 3KDownload > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
