简体   繁体   English

无法在capistrano中部署多个主机

[英]cannot deploy multiple hosts in capistrano

I'm using capistrano to deploy rails app to about 20 servers, it works ok when server num ~ 10, when increase it to >~ 10, it doesnt work anymore 我正在使用capistrano将Rails应用程序部署到大约20台服务器,当服务器数量〜10时工作正常,当将其增加到>〜10时,它不再工作

Here is the error 这是错误

cap aborted!
Errno::EPIPE: Broken pipe
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/net-ssh-3.2.0/lib/net/ssh/transport/server_version.rb:44:in `write'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/net-ssh-3.2.0/lib/net/ssh/transport/server_version.rb:44:in `negotiate!'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/net-ssh-3.2.0/lib/net/ssh/transport/server_version.rb:32:in `initialize'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/net-ssh-3.2.0/lib/net/ssh/transport/session.rb:84:in `new'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/net-ssh-3.2.0/lib/net/ssh/transport/session.rb:84:in `initialize'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/net-ssh-3.2.0/lib/net/ssh.rb:232:in `new'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/net-ssh-3.2.0/lib/net/ssh.rb:232:in `start'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/sshkit-1.11.2/lib/sshkit/backends/connection_pool.rb:59:in `call'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/sshkit-1.11.2/lib/sshkit/backends/connection_pool.rb:59:in `with'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/sshkit-1.11.2/lib/sshkit/backends/netssh.rb:155:in `with_ssh'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/sshkit-1.11.2/lib/sshkit/backends/netssh.rb:49:in `upload!'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/capistrano-3.6.1/lib/capistrano/tasks/git.rake:24:in `block (3 levels) in <top (required)>'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/sshkit-1.11.2/lib/sshkit/backends/abstract.rb:29:in `instance_exec'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/sshkit-1.11.2/lib/sshkit/backends/abstract.rb:29:in `run'
/Users/khiem-nguyen/workspace/ruby/nenga-onepiece/cl-chef/deploy/vendor/bundle/ruby/2.3.0/gems/sshkit-1.11.2/lib/sshkit/runners/parallel.rb:12:in `block (2 levels) in execute'
Tasks: TOP => git:check => git:wrapper
The deploy has failed with an error: Broken pipe
** Invoke deploy:failed (first_time)
** Execute deploy:failed    


** DEPLOY FAILED
** Refer to log/capistrano.log for details. Here are the last 20 lines:    


 DEBUG Uploading /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh 0.0%    

 DEBUG Uploading /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh 0.0%    

  INFO [7c256e12] Running /usr/bin/env chmod 700 /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh on onepiece-web07    

 DEBUG [7c256e12] Command: ( export RBENV_ROOT="$HOME/.rbenv/bin/rbenv" PATH="$HOME/.rbenv/shims:$HOME/.rbenv/bin:$PATH" ; /usr/bin/env chmod 700 /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh )    

  INFO Uploading /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh 100.0%    

  INFO Uploading /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh 100.0%    

  INFO [846397ba] Finished in 0.065 seconds with exit status 0 (successful).    

  INFO [3e8f8a49] Running /usr/bin/env chmod 700 /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh on onepiece-web03    

 DEBUG [3e8f8a49] Command: ( export RBENV_ROOT="$HOME/.rbenv/bin/rbenv" PATH="$HOME/.rbenv/shims:$HOME/.rbenv/bin:$PATH" ; /usr/bin/env chmod 700 /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh )    

  INFO [7c256e12] Finished in 0.037 seconds with exit status 0 (successful).    

  INFO [264aa0db] Running /usr/bin/env chmod 700 /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh on onepiece-web01    

 DEBUG [264aa0db] Command: ( export RBENV_ROOT="$HOME/.rbenv/bin/rbenv" PATH="$HOME/.rbenv/shims:$HOME/.rbenv/bin:$PATH" ; /usr/bin/env chmod 700 /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh )    

  INFO [a8720934] Finished in 0.265 seconds with exit status 0 (successful).    

  INFO [3e8f8a49] Finished in 0.043 seconds with exit status 0 (successful).    

  INFO [264aa0db] Finished in 0.038 seconds with exit status 0 (successful).    

 DEBUG Uploading /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh 0.0%    

  INFO Uploading /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh 100.0%    

  INFO [3d959fa8] Running /usr/bin/env chmod 700 /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh on onepiece-web02    

 DEBUG [3d959fa8] Command: ( export RBENV_ROOT="$HOME/.rbenv/bin/rbenv" PATH="$HOME/.rbenv/shims:$HOME/.rbenv/bin:$PATH" ; /usr/bin/env chmod 700 /tmp/git-ssh-nenga-onepiece-production-khiem-nguyen.sh )    

  INFO [3d959fa8] Finished in 0.045 seconds with exit status 0 (successful).

I think there's something related to ssh max connection??? 我认为有一些与ssh max连接有关的信息???

Cap version:3.6.1 SSH kit: 1.9.0 上限版本:3.6.1 SSH套件:1.9.0

SSHKit (the SSH layer in Capistrano) uses connection pooling. SSHKit(Capistrano中的SSH层)使用连接池。 This means that it maintains an SSH connection for each host. 这意味着它为每个主机维护一个SSH连接。 If you are seeing a broken pipe error when you increase the hosts, the only thing I can think of is that perhaps a firewall or gateway (ie an ssh proxy) is limiting the number of simultaneous connections. 如果您在增加主机时看到管道断开错误,那么我唯一想到的可能是防火墙或网关(即ssh代理)限制了同时连接的数量。

As a workaround, you can try disabling the connection pool. 解决方法是,您可以尝试禁用连接池。 Add the following to your deploy.rb : 将以下内容添加到您的deploy.rb

# Disable connection pool
SSHKit::Backend::Netssh.pool.idle_timeout = 0

This will make your deployments slower, but it might solve the connection errors. 这将使您的部署速度变慢,但可以解决连接错误。

You could try tweaking MaxStartups in /etc/ssh/sshd_config on the server of your Git server. 您可以尝试在Git服务器的服务器上的/ etc / ssh / sshd_config中调整MaxStartups。

Default value is 10:30:60, the first 10 limits this. 默认值为10:30:60,前10个限制了此值。

MaxStartups Specifies the maximum number of concurrent unauthenticated con- nections to the sshd daemon. MaxStartups指定与sshd守护程序的未认证并发连接的最大数量。 Additional connections will be dropped until authentication succeeds or the LoginGraceTime expires for a connection. 其他连接将被丢弃,直到身份验证成功或该连接的LoginGraceTime过期为止。 The default is 10. 预设值为10。

    Alternatively, random early drop can be enabled by specifying the
    three colon separated values "start:rate:full" (e.g.,
    "10:30:60").  sshd will refuse connection attempts with a proba-
    bility of "rate/100" (30%) if there are currently "start" (10)
    unauthenticated connections.  The probability increases linearly
    and all connection attempts are refused if the number of unau-
    thenticated connections reaches "full" (60).

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM