Crash Data
Introduction
A process core dump file contains the recorded status of the working memory of the Gaia computer at the time that a Gaia process terminated abnormally.
When a process terminates abnormally, it produces a core dump file in the /var/log/dump/usermode/ directory.
If the /log partition has less than 200 MB, Gaia OS does not create new core dump files and deletes the existing core dump files to get more free space. This prevents the core dump files from filling the /log partition.
|
|
Warning - The core dump files may contain personal data. For more information, see sk175504. |
Configuring Core Dumps in Gaia Portal
|
|
Important - On Scalable Platforms (ElasticXL, Maestro, and Chassis), you must connect to the Gaia Portal of the applicable Security Group. |
Watch the Video
To configure core dumps, enable the feature and then configure parameters.
Procedure
|
Step |
Instructions |
|---|---|
|
1 |
In the navigation tree, click System Management > Crash Data. |
|
2 |
Select Enable Core Dumps and configure the parameters. |
|
3 |
In the Total space limit field, configure the maximum disk space to keep all core dump files. Gaia OS deletes the oldest core dump file if it requires disk space for a new core dump file. Gaia OS enforces the process limit before the space limit.
Based on the enabled features, Gaia OS may change the default value automatically. To see the current value, run this command in Gaia Clish:
|
|
4 |
In the Dumps per process field, configure the maximum number of core dump files to keep for each process executable file. A new core dump file overwrites the oldest core dump file. Gaia OS enforces the process limit before the space limit.
Example
There are two user space processes "A" and "B", and the limit is 2 core dump files for each process. Process "A" terminates 1 time, and process "B" terminates 3 times. Gaia OS keeps these core dumps:
Gaia OS deletes the core dump #3 for process "B" because of the process limit. |
|
5 |
Click Apply. |
Configuring Core Dumps in Gaia Clish
|
|
Important - On Scalable Platforms (ElasticXL, Maestro, and Chassis), you must run the applicable commands in Gaia gClish of the applicable Security Group. |
Syntax
-
To enable or disable core dump files:
set core-dump {enable | disable} -
To configure the total disk space limit for all core dump files (in MB):
set core-dump total <0-99999> -
To configure the number of core dump files for each process:
set core-dump per_process <0-99999> -
To show the status of this feature:
show core-dump status -
To show the configured total disk space limit:
show core-dump total -
To show the configured limit of core dump files for each process:
show core-dump per_process
|
|
Important - After you add, configure, or delete features, run the " |
Parameters
|
Parameter |
Description |
|---|---|
|
|
The maximum disk space to keep all core dump files. Gaia OS deletes the oldest core dump file if it requires disk space for a new core dump file. Gaia OS enforces the process limit before the space limit.
Based on the enabled features, Gaia OS may change the default value automatically. To see the current value, run this command in Gaia Clish:
|
|
|
The maximum number of core dump files to keep for each process executable file. A new core dump file overwrites the oldest core dump file. Gaia OS enforces the process limit before the space limit.
Example
There are two user space processes "A" and "B", and the limit is 2 core dump files for each process. Process "A" terminates 1 time, and process "B" terminates 3 times. Gaia OS keeps these core dumps:
Gaia OS deletes the core dump #3 for process "B" because of the process limit. |