Core Dumps

Introduction

A process core dump file consists of the recorded status of the working memory of the GaiaClosed Check Point security operating system that combines the strengths of both SecurePlatform and IPSO operating systems. 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, no core dumps are created, and all core dumps are deleted to create space. This prevents the core dump files from filling the /log partition.

Configuring Core Dumps in Gaia Portal

Note - You must connect to the Gaia PortalClosed Web interface for the Check Point Gaia operating system. of the applicable Security GroupClosed A logical group of Security Appliances that provides Active/Active cluster functionality. A Security Group can contain one or more Security Appliances. Security Groups work separately and independently from each other. To the production networks, a Security Group appears a single Security Gateway. Every Security Group contains: (A) Applicable Uplink ports, to which your production networks are connected; (B) Security Appliances (the Quantum Maestro Orchestrator determines the applicable Downlink ports automatically); (C) Applicable management port, to which the Check Point Management Server is connected..

To configure core dumps, enable the feature and then configure parameters.

Step

Instructions

1

In the navigation tree, click System Management > Core Dumps.

2

Configure the parameters.

3

Click Apply.

Parameter

Description

Total space limit

The maximum amount of disk space in MB that is used for storing core dumps.

If disk space is required for a core dump, the oldest core dump is deleted.

The per-process limit is enforced before the space limit.

  • Range: 1 - 99999 MB

  • Default: 1000 MB

Dumps per process

The maximum number of dumps that are stored for each process executable (program) file.

A new core dump overwrites the oldest core dump.

The per-process limit is enforced before the space limit.

  • Range: 1 - 99999

  • Default: 2

There are two programs "A" and "B", and the per-process limit is limit is 2.

Program "A" terminates 1 time and program "B" terminates 3 times.

The core dumps that remain are:

  • 1 core dump for program "A"

  • 2 core dumps for program "B"

  • Core dump 3 for program "B" is deleted because of the per-process limit.

Configuring Core Dumps in Gaia Clish

Note - You must run these commands in Gaia gClishClosed The name of the global command line shell in Check Point Gaia operating system for Security Appliances connected to Check Point Quantum Maestro Orchestrators. Commands you run in this shell apply to all Security Appliances in the Security Group. of the applicable Security Group.

  • To enable or disable core dumps:

    set core-dump {enable | disable}

  • To set the total disk space usage limit in MB:

    set core-dump total <0-99999>

  • To set the number of core dumps per process:

    set core-dump per_process <0-99999>

  • To show the total disk space usage limit:

    show core-dump total

  • To show the number of core dumps per process:

    show core-dump per_process

Important - After you add, configure, or delete features, run the "save config" command to save the settings permanently.

Parameter

Description

total <0-99999>

The maximum amount of space that is used for core dumps. If space is required for a dump, the oldest dump is deleted.

The per-process limit is enforced before the space limit.

  • Range: 1 - 99999 MB

  • Default: 1000 MB

per_process <0-99999>

The maximum number of core dumps that are stored for each process executable (program) file.

A new core dump overwrites the oldest core dump.

The per-process limit is enforced before the space limit.

  • Range: 1 - 99999

  • Default: 2

There are two programs "A" and "B", and the per-process limit is limit is 2.

Program "A" terminates 1 time and program "B" terminates 3 times.

The core dumps that remain are:

  • 1 core dump for program "A"

  • 2 core dumps for program "B"

  • Core dump 3 for program "B" is deleted because of the per-process limit.