2016-11-08 28 views
0

我使用Capistrano的部署Rails应用程序到约20台服务器上部署多台主机,它的工作原理确定,当服务器NUM〜10,当增加它>〜10,它不工作了不能Capistrano的

这里错误

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). 

我认为有什么与ssh max connection有关?

CAP版本:3.6.1 SSH试剂盒:1.9.0

+0

我建议按照错误消息中的说明重新运行带有'--trace'标志的部署。这将提供有关错误发生位置的更多信息。请同时发布您正在使用的Capistrano和SSHKit版本。 –

+0

我刚刚在这里添加了跟踪日志和上限版本。请帮忙 – KhiemNS

回答

0

您可以尝试在Git服务器的服务器上的/ etc/ssh/sshd_config中调整MaxStartups。

默认值是10:30:60,前10个限制这个。

MaxStartups 指定与sshd守护进程并发的未经身份验证的最大并发连接数。其他连接将被丢弃,直到身份验证成功或连接的LoginGraceTime 失效。缺省值为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). 
0

SSHKit(在Capistrano的所述SSH层)使用连接池。这意味着它为每个主机维护一个SSH连接。如果在增加主机时发现管道出现故障,我唯一能想到的就是防火墙或网关(即ssh代理)可能会限制同时连接的数量。

作为解决方法,您可以尝试禁用连接池。以下内容添加到您的deploy.rb

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

这将使您的部署速度较慢,但​​它可能会解决连接错误。

+0

我发现原因是git服务器的连接限制。非常感谢 – KhiemNS