It's really just a matter of running cap again. The error (when it happens) happens very early, before anything has actually happened on the remote server(s), so your servers should be exactly as you left them. The error, though annoying, is "safe" in that regard.

- Jamis

On Dec 5, 2007, at 11:25 AM, DeRailed wrote:


Hi Jamis,

  Thanks for the info. I am pushing some mission critical files over
to these servers. Can you think of a sturdier solution in the
interim ?

Regards,
Fernand

On Dec 5, 10:54 am, Jamis Buck <[EMAIL PROTECTED]> wrote:
Fernand,

I get this periodically, too, and have not had a chance to
investigate. It is definitely related to the order in which services
are loaded by Needle, so it will become a non-issue when I finally
complete the rewrite of Net::SSH and friends. (Wish I could commit to
a date when that would happen, but...)

For the short-term, I suspect something more needs to be added to the
(large) list of modules that need to be eagerly loaded in capistrano/
ssh.rb.

- Jamis

On Dec 5, 2007, at 10:28 AM, DeRailed wrote:



Hi Jamis,

 I have a capistrano recipe to push files on a set of servers using
the following cap task:

  execute_on_servers( {} ) do |servers|
    servers.each do |server|
      logger.info "Pushing file #{dump_file} to #{server} --
#{destination_dir}"
      `rsync -avz --delete #{zip_file}
[EMAIL PROTECTED]:#{destination_dir}`
    end

 This works most of the time. However once in a while I am getting
the following error:

connection failed for: x.x.x.x (NoMethodError: undefined method
`register_services' for Net::SSH::Service::Process:Module)

  I am using Cap 2.1.0 and net-ssh 1.1.2

  Do you have any suggestions on how to fix this ?

Thanks,
Fernand



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
-~----------~----~----~----~------~----~------~--~---


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to