CloudShell Colony keeps multiple deployment logs for your application deployments. In case the sandbox deployment fails, you can review these logs by connecting to your compute instance and browsing the log files.

For instructions on remotely connecting to the relevant compute instances, see Connecting to Compute Instances Using SSH or RDP.

CloudShell Colony keeps the following log files:

NOTE ABOUT TROUBLESHOOTING THE START SCRIPT: To minimize CloudShell Colony's intervention in the execution of your applications, we do not log start script executions. Therefore, if you need to debug this script (e.g. the application did not start), please connect to the instance, manually rerun the script and check the application deployment logs.

Browsing logs in Linux VMs

Browsing the deployment logs is done using a lightweight utility that CloudShell Colony automatically installs on your Linux machines which is accessible from a bash command line shell. 

To print the deployment logs that ran on a specific VM to the shell output, use the following command:

colony.sh logs

In case of multiple applications installed on a single VM, all the log files of all applications will be printed one after the other. To filter a specific log file, use:

grep –i

Here are three examples of this use:

colony.sh logs | grep –i eventsrep –i

colony.sh logs | grep –i initialization

colony.sh logs | grep –i healthcheck

In case of multiple applications installed on a single VM, all the log files of all applications will be printed one after the other. To filter a specific application, use the following command:

colony.sh logs [application name]