[Capistrano] Re: ConnectionError, connection failed - update

[Jamis Buck]

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

smime.p7s
Description: S/MIME cryptographic signature