Engine Yard Developer Center

Site is Down: Diagnostic Checklist

If your site is down, here are some things to try. If these don’t work, submit a ticket with Engine Yard Support.

Can you access the Dashboard via http://cloud.engineyard.com?

  • If not, go to @eycloud to see if Engine Yard Cloud has problems.

After you have logged in, does your application show red status circles?

  • If yes, these red circles usually indicate problems with the instance.
    • Check the Base log (log output for Engine Yard’s Chef scripts) and the Custom log (log output for your custom Chef scripts). You can find configuration problems in the logs.
      • Solution: Fix these and click Apply to re-run these scripts.
    • Review the Alerts on the Environment page. These indicate if the instance has issues with its resources.
      • Note: Alerts are enabled by default but, to receive email notification, enable email alerts.
      • Solution: If your application is using too many resources and causing alerts, you can move to a larger instance size or reconfigure your environment to not use so many resources on one instance.

Click View Log and review the log to make sure that the most recent deployment log was successful.

If none of these have alerted to the problem, then SSH into your instance and check these items:

Go to /data/<appname>/current/log and view your application log. This log indicates if there are problems with your running application.

$ cd /data/myapp/current/log 
$ tail production.log

 If you have a cluster of instances, make sure that HAProxy is running:

$ ps ax|grep haproxy

 If HAProxy is not running, run /etc/init.d/haproxy start.

On your application instances, make sure that Nginx is running:

$ sudo /etc/init.d/nginx status 
* status: started

 If Nginx is not running, run sudo /etc/init.d/nginx start.

 On your application instances, if using Passenger, make sure Passenger is running:

$ passenger-status 

If Passenger is not running, restart Nginx:

$ sudo /etc/init.d/nginx restart 

On your single instance or database instance, make sure that the database running:

  • For a PostgreSQL 9.1 database:

    $ sudo /etc/init.d/postgresql-9.1 status

    If PostgreSQL is not running, restart PostgreSQL:

    $ sudo /etc/init.d/postgresql-9.1 start
  • For a MySQL database:

    $ sudo /etc/init.d/mysql status 

    If MySQL is not running, restart MySQL:

    $ sudo /etc/init.d/mysql start 

If you have feedback or questions about this page, add a comment below. If you need help, submit a ticket with Engine Yard Support.

Was this article helpful?
11 out of 11 found this helpful
Have more questions? Submit a request

Comments

Please sign in to leave a comment.

Powered by Zendesk