> Source: [sk93587](https://support.checkpoint.com/results/sk/sk93587)

# sk93587 - The output of the 'top' command on the Gaia OS shows that the 'monitord' process consumes memory or CPU at a high level

| Property | Value |
|----------|-------|
| Solution ID | sk93587 |
| Date Created | 2013-07-15 |
| Last Modified | 2024-05-02 |
| Technical Level | General |
| Products | Security Gateway, Security Management Server, Multi-Domain Security Management Server |
| Versions | R81.20, R81.10 (EOS), R81.20, R81 (EOS), R81.10 (EOS), R81 (EOS), R81 (EOS), R81.10 (EOS), R81.20 |
| OS | Gaia |

## Symptoms

- * The output of the `top` command on the Gaia OS shows that the `monitord` process consumes memory or CPU at a high level.

* The size of the `/var/log/db` file increases constantly.

## Cause

The hardware monitor's history, the `/var/log/db` file, contains sensors' data from a period of 1 year ago. If the Check Point software was upgraded, the SQL database needs to be rebuilt.

## Solution

This problem was fixed. The fix is included in:

* [Check Point R80.10](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk111841)

Check Point recommends to always upgrade to the most recent version ([upgrade Security Gateway](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=435) / [upgrade Cluster](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=428) / [upgrade Security Management Server](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=184) / [upgrade Multi-Domain Security Management Server](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=downloads&product=166)).

<br />

If you do not wish to upgrade, to resolve the problem, check the size of the*/var/log/db* file. If it is bigger than 100M, back it up and remove it. Also check the CPU consumption for the *monitord* process.

**Procedure**

1. Log in to the command line on the machine and log in to the Expert mode.   

2. Terminate the `monitord` process:   

   **`[Expert@HostName]# tellpm process:monitord`**   

3. Backup the current `/var/log/db` file:   

   **`[Expert@HostName]# cp /var/log/db /var/log/db_ORIGINAL`**   

4. Reduce the size of hardware monitor's history SQL database:   

   **`[Expert@HostName]# sqlite3 /var/log/db`**   

   Run the following commands in the `sqlite` prompt:   

   `sqlite> `**VACUUM;**  
   `sqlite> `**.exit**   

5. Start the `monitord` daemon (notice the '`t`' flag in the end):   

   **`[Expert@HostName]# tellpm process:monitord t`**

**Notes:**

* Sometimes only removing the database file may be enough. Therefore, instead of Step 3, simply delete the database file with the '`rm /var/log/db`' command and continue to Step 5. New database file will be automatically recreated after daemon starts (this can take several minutes to complete, depending on the database size).   
  If deleting the database file does not help, perform the complete procedure, including Step 3.  

* If Step 4 does not help, proceed with deleting the database file.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
