Crash Reporting Configuration

You can manage crash reporting for the Editor Application using the following options:

1. Disabling Crash Reporting:

   • To disable crash reporting, start the server with the -no-crash flag:

     /etc/init.d/editor start -no-crash

2. Configuring S3 Bucket for Crash Dumps:

   • To collect crash dumps on an S3 bucket, configure the following parameters in the /etc/init.d/editor file:

     • CRASHBUCKETREGION

     • CRASHBUCKET

     • PRODUCT

   • For example, to accumulate crash dumps to the "graebert-crashes" S3 bucket in the "us-east-1" region for the "xenon-editor" product, configure as follows:

     CRASHBUCKETREGION="us-east-1"
CRASHBUCKET="graebert-crashes"
PRODUCT="xenon-editor"

   • Start the server normally after configuring these parameters:

     /etc/init.d/editor start

Note:

• Disabling crashes or incorrectly configuring S3 may lead to the system folder /var/crash being flooded with dumps, especially if the system generates numerous crashes. It is advisable to clear dumps via a cron job at regular intervals (e.g., every 30 minutes) to prevent this from happening.