本文介绍了Engineyard命令行:ey web重新启动不起作用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

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

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 -v2.4.6

rvm -vrvm 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重新启动不起作用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

05-31 21:46