Viewing logs from your environment

The build hooks and the deploy hooks produce logs that can be helpful in troubleshooting issues.

Build logs

After pushing code to your environment, you can see the results of both hooks. Logs from the build hook are redirected to the output stream of git push, so you can observe them in the terminal or capture them (along with error messages) using the command git push > build.log 2>&1.

Deploy logs

Logs from the deployment hook are located on the server. The location depends on whether it is an integration environment or a staging/production environment.

  • Integration environments: /tmp/log/deploy.log
  • Staging or production: /var/log/platform/<user>/post_deploy.log

The value of <user> depends on the project ID and whether the environment is staging or production. For example, if the project ID is yw18fW0Xjcawe, the staging environment user is yw18fW0Xjcawe_stg and the production environment user is yw18fW0Xjcawe.

On a staging environment for project yw18fW0Xjcawe, the deploy log is located at /var/log/platform/yw18fW0Xjcawe_stg/post_deploy.log.

Logs for all deployments that have happened on this environment are appended to this file, so check the timestamps on log entries to verify that you’re seeing the logs that correspond to the deployment that you are interested in.

Log output is highly verbose to allow troubleshooting. For example:

[2016-10-11 22:15:38] Starting pre-deploy.
...
[2016-10-11 22:15:39] Pre-deploy complete.
[2016-10-11 22:15:42] Start deploy.
[2016-10-11 22:15:42] Preparing environment specific data.
[2016-10-11 22:15:42] Initializing routes.

... more ...

[2016-10-11 22:15:46] Deployment complete.

The deploy log contains start and stop messages for each of the two hooks: Starting pre-deploy, Pre-deploy complete., Start deploy., and Deployment complete..