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

# sk184337 - Check Point-specific CLI commands take a long time to execute

| Property | Value |
|----------|-------|
| Solution ID | sk184337 |
| Date Created | 2025-11-18 |
| Last Modified | 2025-11-19 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82, R81.20 |
| OS | Gaia |

## Symptoms

- * Check Point-specific CLI commands such as `cphaprob stat`, `cpstat`, `fw stat`, and `cpview` take 20--40 seconds to execute.

* The issue affects both cluster members: Active and Standby.

* The CPView utility displays `N/A` for CPU and memory utilization values.

  Note: The `cpview` utility monitors and displays real-time statistics about system performance and resource usage. The `CPVIEWD` daemon powers the CPView utility.
* The `/var/log/messages` file contains many `spike_detective` log entries, indicating that `CPVIEWD` threads are causing CPU spikes:

  Example Log Entry:

  `spike_detective: Detected CPU spike on core 3 caused by cpviewd thread`

  Note: Stopping the `CPVIEWD` process immediately restores correct CLI performance.

## Cause

An issue in the internal statistics collection threads of the `CPVIEWD `daemon can cause excessive CPU consumption, resulting in significant delays when running Check Point-specific CLI commands.

## Solution

[Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing it.  
For faster resolution and verification, collect these files:

1. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Management Server involved in the case.
2. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Security Gateway / each Cluster Member / Security Group involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://support.checkpoint.com/results/sk/sk168597).

This **workaround**is also available:

1. Stop the `CPVIEWD ` daemon:  
   `[Expert@HostName]# cpwd_admin stop -name CPVIEWD`

2. Start the `CPVIEWD ` daemon:  
   `[Expert@HostName]# cpwd_admin start -name CPVIEWD -path "$CPDIR/bin/cpviewd" -command "cpviewd"`

3. If you see a "`Process CPVIEWD failed on start`" error, then follow these additional steps:

   1. Disable CPView history logging:  
      `[Expert@Hostname]# cpview -s off`

   2. Start the `CPVIEWD `daemon again:  
      `[Expert@HostName]# cpwd_admin start -name CPVIEWD -path "$CPDIR/bin/cpviewd" -command "cpviewd"`

   3. Enable the CPView history daemon:  
      `[Expert@Hostname]# cpview -s on`

4. Verify that the `CPVIEWD `daemon is running (the `STAT` column must show `E`):  
   `[Expert@HostName]# cpwd_admin list | grep -E "APP|CPVIEWD"`

---

# 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