내 환경에 내 Rails 앱 배포를 성공적으로 완료했지만 모니터링 대시 보드에 0.0 ELB 인스턴스가있는 것을 볼 수 있는데 그 이유는 무엇입니까?
배포 할 때 내 로그는 다음과 같습니다.
INFO: Deploying new version to instance(s).
INFO: New application version was deployed to running EC2 instances.
INFO: Environment update completed successfully.
현재 내 앱을 방문 할 때만 빈 페이지가 표시됩니다. 0.0 ELB 인스턴스가 있기 때문이라고 가정합니다.
어떻게 해결할까요?
다음은 스냅 샷입니다.
편집, 활동 로그 :
[2015-08-23T17:18:03.570Z] INFO [18661] - [Application update/AppDeployStage1/AppDeployEnactHook/99_reload_app_server.sh] : Starting activity...
[2015-08-23T17:18:04.993Z] INFO [18661] - [Application update/AppDeployStage1/AppDeployEnactHook/99_reload_app_server.sh] : Completed activity. Result:
+ service passenger restart
According to the PID file '/var/app/support/pids/passenger.pid',
Phusion Passenger Standalone doesn't seem to be running.
If you know that Phusion Passenger Standalone *is* running then one of these
might be the cause of this error:
* The Phusion Passenger Standalone instance that you want to stop isn't running
on port 80, but on another port. If this is the case then you
should specify the right port with --port.
If the instance is listening on a Unix socket file instead of a TCP port,
then please specify the PID file's filename with --pid-file.
* The instance that you want to stop has stored its PID file in a non-standard
location. In this case please specify the right PID file with --pid-file.
/opt/elasticbeanstalk/support/conf/nginx_config_healthd.erb:49:in `block in write_nginx_config_file': undefined local variable or method `location_config_filename' for #<PhusionPassenger::Standalone::StartCommand:0x007f7ab$
from /opt/rubies/ruby-2.2.2/lib/ruby/2.2.0/erb.rb:863:in `eval'
from /opt/rubies/ruby-2.2.2/lib/ruby/2.2.0/erb.rb:863:in `result'
from /opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/standalone/start_command/nginx_engine.rb:120:in `block in write_nginx_config_file'
from /opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/standalone/start_command/nginx_engine.rb:113:in `open'
from /opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/standalone/start_command/nginx_engine.rb:113:in `write_nginx_config_file'
from /opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/standalone/start_command/nginx_engine.rb:41:in `start_engine_real'
from /opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/standalone/start_command.rb:609:in `start_engine'
from /opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/standalone/start_command.rb:80:in `run'
from /opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/standalone/main.rb:50:in `run!'
from /opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/bin/passenger:44:in `<top (required)>'
from /opt/rubies/ruby-2.2.2/bin/passenger:23:in `load'
from /opt/rubies/ruby-2.2.2/bin/passenger:23:in `<main>'
[2015-08-23T17:18:04.993Z] INFO [18661] - [Application update/AppDeployStage1/AppDeployEnactHook] : Completed activity. Result:
Successfully execute hooks in directory /opt/elasticbeanstalk/hooks/appdeploy/enact.
향상된 건강을 사용하고있는 것 같습니다. 대시 보드 링크를 클릭 할 수 있습니다. 원인 버튼이 표시됩니다. 원인 버튼을 클릭하면 환경 상태가 심각한 이유를 알 수 있습니다. https://aws.amazon.com/blogs/aws/elastic-beanstalk-update-enhanced-application-health-monitoring/ 에서 원인 버튼을 찾는 예제 스크린 샷을 참조하십시오.
이 기사는 인터넷에서 수집됩니다. 재 인쇄 할 때 출처를 알려주십시오.
침해가 발생한 경우 연락 주시기 바랍니다[email protected] 삭제
몇 마디 만하겠습니다