0

带有橡胶部署错误的 Amazon ec2。当我运行 create staging 时,出现以下错误。

/usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/middlewares/expects.rb:10:in response_call': Unable to find group 'Matchimi_Enterprise_production_default' (Fog::Compute::AWS::NotFound) from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/connection.rb:353:inresponse' from /usr/local/rvm/gems/ ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/connection.rb:247:in request' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/middlewares/idempotent.rb:12:inerror_call' 来自 /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon -0.23.0/lib/excon/middlewares/base.rb:10:in error_call' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/connection.rb:260:inrescue in request' 来自 /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/ excon/connection.rb:220:in request' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/middlewares/idempotent.rb:12:inerror_call' 来自 /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/middlewares/base.rb:10:inerror_call' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/connection.rb:260:in来自 /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/connection.rb:220:in request' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/middlewares/idempotent.rb:12:inerror_call' 的救援请求'来自 /usr/local/rvm /gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/middlewares/base.rb:10:inerror_call' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/connection.rb:260:in来自 /usr/local/rvm/gems/ruby-1.9.3-p392/gems/excon-0.23.0/lib/excon/connection.rb:220:in request' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/fog-1.12.1/lib/fog/core/connection.rb:25:inrequest' 的救援请求'来自 /usr/local/rvm /gems/ruby-1.9.3-p392/gems/fog-1.12.1/lib/fog/aws/compute.rb:385:in _request' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/fog-1.12.1/lib/fog/aws/compute.rb:380:inrequest' 来自 /usr/local/rvm/gems/ruby-1.9.3- p392/gems/fog-1.12.1/lib/fog/aws/requests/compute/authorize_security_group_ingress.rb:54:in authorize_security_group_ingress' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/fog-1.12.1/lib/fog/aws/models/compute/security_group.rb:104:inauthorize_port_range' 来自 /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber -2.5.2/lib/rubber/cloud/aws.rb:368:in add_security_group_rule' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber-2.5.2/lib/rubber/cloud/aws.rb:500:inblock (2 levels) in sync_security_groups' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber-2.5. 2/lib/rubber/cloud/aws.rb:496:in each' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber-2.5.2/lib/rubber/cloud/aws.rb:496:inblock in sync_security_groups' 来自 /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber-2.5.2/lib/rubber/cloud /aws.rb:490:ineach' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber-2.5.2/lib/rubber/cloud/aws.rb:490:insync_security_groups' 来自 /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber-2.5.2/lib/rubber/cloud/aws.rb:254:in setup_security_groups' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber-2.5.2/lib/rubber/cloud/aws.rb:72:inbefore_create_instance' 来自 /usr/local/rvm /gems/ruby-1.9.3-p392/gems/rubber-2.5.2/lib/rubber/thread_safe_proxy.rb:13:in method_missing' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber-2.5.2/lib/rubber/recipes/rubber/instances.rb:267:inblock in create_instance' 来自 /usr/local/rvm/rubies/ruby-1.9.3- p392/lib/ruby/1.9.1/monitor.rb:211:in mon_synchronize' from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber-2.5.2/lib/rubber/recipes/rubber/instances.rb:266:increate_instance' 来自 /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rubber-2.5.2/lib/rubber/recipes /rubber/instances.rb:230:in `block (2 levels) in create_instances'

4

2 回答 2

1

它发生在我身上,原因是我在帐户字段中使用了我的用户名,而不是我的 AWS 帐号。我假设如果帐号错误,则会出现类似的错误。

于 2013-11-29T09:13:43.193 回答
0

我得到了解决方案。

我从我的 gem 文件中删除了带有 github 链接的 gem。我发现有时如果你关联从 github 定向的 gem,如果那个 github 链接关闭,你会得到部署错误。因此,应避免在您的 gemfile 中添加 github 链接以保存在部署中。

于 2014-08-12T07:02:39.053 回答