Hello David,
thanks for the kind answer,
On Feb 20, 11:42 pm, "David Masover" <[EMAIL PROTECTED]>
wrote:
> Long answer: The Capfile, and config/deploy.rb if you're using that, are
> valid Ruby.
that's good news.
> in your Capfile (or deploy.rb).
i still haven't understand which one should I use. i don't have any
deploy.rb file yet.
> File.open 'some_file' do |file|
> file.each_line do |line|
> role :peers, line.chomp
> end
> end
this works fine.
> role :peers do
> servers = []
> File.open 'some_file' do |file|
> file.each_line do |line|
> servers << line.chomp
> end
> end
> servers
> end
that would be even better.
Stll, my deployment hangs when the number of nodes increases..doing a
ctrl^c produces this:
* establishing connection to `ita23.imag.fr' via gateway
* establishing connection to `ita24.imag.fr' via gateway
* establishing connection to `ita27.imag.fr' via gateway
* establishing connection to `ita5.imag.fr' via gateway
* establishing connection to `ita7.imag.fr' via gateway
* establishing connection to `ita8.imag.fr' via gateway
* establishing connection to `ita9' via gateway
connected: `ita16.imag.fr' (via gateway)
connected: `ita22.imag.fr' (via gateway)
connected: `ita18.imag.fr' (via gateway)
connected: `ita27.imag.fr' (via gateway)
connected: `ita24.imag.fr' (via gateway)
connected: `ita23.imag.fr' (via gateway)
connected: `ita9' (via gateway)
connected: `ita7.imag.fr' (via gateway)
connected: `ita8.imag.fr' (via gateway)
^C/opt/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/lib/capistrano/
configuration/connections.rb:87:in `join': Interrupt
from /opt/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/lib/
capistrano/configuration/connections.rb:87:in
`establish_connections_to'
from /opt/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/lib/
capistrano/configuration/connections.rb:87:in `each'
from /opt/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/lib/
capistrano/configuration/connections.rb:87:in
`establish_connections_to'
from /opt/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/lib/
capistrano/configuration/connections.rb:125:in `execute_on_servers'
from /opt/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/lib/
capistrano/configuration/actions/invocation.rb:51:in `run'
from ./Capfile:31:in `load'
from /opt/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/lib/
capistrano/configuration/execution.rb:80:in `instance_eval'
from /opt/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/lib/
capistrano/configuration/execution.rb:80:in
`execute_task_without_callbacks'
... 7 levels...
from /opt/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/lib/
capistrano/cli/execute.rb:14:in `execute'
from /opt/local/lib/ruby/gems/1.8/gems/capistrano-2.1.0/bin/cap:4
from /usr/bin/cap:16:in `load'
from /usr/bin/cap:16
If I debunk correctly the stacktrace, the problem "might" seems to
derive from one of the machines on the cluster not responding
promptly, thus causing the join method to wait..somehow forever..
I wonder if some sort of timeout value can be set before a given
connection is completely discarded.
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
