Engineyard命令行：ey web重新启动不起作用 [英] Engineyard command line: ey web restart not working

问题描述

我最近安装了engineyard gem。当我尝试运行'ey web restart'时，出现以下错误：

/home/jplato/.rvm/gems/ruby -2.2.0 / gems / engineyard-3.1.2 / lib / engineyard / thor.rb：32：
警告：循环参数引用 - serverside_version从Engine Yard Cloud加载
应用程序数据...重新启动服务器on
jplato / my_app / Rails4

'serverside_version'
的值必须非空。

blockquote>

尝试设置环境变量ENGINEYARD_SERVERSIDE_VERSION = 2.2.0，以匹配服务器端适配器gem版本，但它不起作用。其他不使用这个变量的ey命令（比如ey状态）工作正常。

以下是我的开发机器环境的一些信息：
OS： Ubuntu 14.04 b
$ b

gem -v
2.4.6

rvm -v
rvm 1.26.10

gem list --local

• engineyard（3.1.2 ）


• engineyard-cloud-client（2.1.1）
  
• engineyard-serverside-adapter（2.2.0）
  
• thor（0.19.1）

解决方案

尝试推出部署应用程序与engineyard宝石本身，而不是通过仪表板。这可能会迫使engineyard-serverside的版本更新。我不能保证这会起作用，但你可以做的一件事是排除问题（如果你还没有的话）。当部署经过仪表板时，它可能会使用不同版本的engineyard-serverside，而不是通过CLI推送它。这个engineyard-serverside gem是协调应用程序服务器本身的反弹。

或者，您可以运行：

  ey ssh/ engineyard / bin / app_< appname> restart-e your_env_name --app-servers 
  

$ b $ p让engineyard gem在名为your_env_name的环境中运行该脚本（它将重新启动您的应用程序服务器 - 例如Unicorn等），并仅在应用程序服务器上运行该命令。 （当然，一定要真正用你的应用程序名替换< appname>）。

如果仍然失败，你应该打开支持票，因为可能还有别的东西有点时髦去那里。祝你好运！

I recently installed the engineyard gem. When I try to run 'ey web restart', I get the following error:

/home/jplato/.rvm/gems/ruby-2.2.0/gems/engineyard-3.1.2/lib/engineyard/thor.rb:32: warning: circular argument reference - serverside_version Loading application data from Engine Yard Cloud... Restarting servers on jplato / my_app / Rails4

Value for 'serverside_version' must be non-empty.

Tried setting the environment variable ENGINEYARD_SERVERSIDE_VERSION=2.2.0, to match the serverside adapter gem version, but it didn't work. The other ey commands that don't use this variable (such as ey status) work fine.

Here's some info on my dev machine environment: OS: Ubuntu 14.04

gem -v 2.4.6

rvm -v rvm 1.26.10

gem list --local

• engineyard (3.1.2)
• engineyard-cloud-client (2.1.1)
• engineyard-serverside-adapter (2.2.0)
• thor (0.19.1)

解决方案

Try pushing out a deploy of your application with the engineyard gem itself instead of through the dashboard. That may force the version of engineyard-serverside to be more up to date. I can't guarantee that'll work, but it's one thing you can do to rule things out (if you haven't already). When a deploy goes through the dashboard, it may use a different version of engineyard-serverside than if you push it through the CLI. That engineyard-serverside gem is what orchestrates the "bounce" of the app server itself.

Alternatively, you can run:

ey ssh "/engineyard/bin/app_<appname> restart" -e your_env_name --app-servers

to have the engineyard gem run that script (which restarts your app server - e.g. Unicorn, etc.) on the environment named "your_env_name" and only run the command on application servers. (Be sure to actually substitute your application name for < appname > of course.)

If that still fails, you should probably open a support ticket because there's likely something else kinda funky going on there. Good luck!

这篇关于Engineyard命令行：ey web重新启动不起作用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！