Managing log files

Overview

When Cloud 66 provisions servers, we automatically configure logging for various services. There are several logs available for different server components. Depending on the specifics of your application, log names and directories may vary. The information below is for a typical case.

Rails applications

Default Rails deployments

Default Rails deployments on Cloud 66 use Passenger (via Nginx) and the logs are stored in $STACK_PATH/log:

Custom Rails deployments

If you are using a custom web server, such as Puma, Thin or Unicorn then your log file paths will depend on whether your servers use systemd or Bluepill to manage processes. To check this:

Servers using systemd

Servers using Bluepill (legacy)

Other

Log rotation

Your logs in $STACK_PATH/log and /var/log are automatically rotated on a daily basis and by default kept for 14 days into a sub-directory called archive/ in each respective directory. These logs are compressed, and can be uncompressed with the following command: gzip -d <log_file>.log.gz.

Note

You can set the frequency and the number of rotations to be kept using toolbelt.