High CPU on the CMID process when ICAP Client is enabled on Security Gateway

Product: Security Gateways
Version: R81.10 (EOS), R81.20, R82, R82.10
Last Modified: 2026-07-23

Symptoms

• After enabling ICAP Client on a Check Point Security Gateway, CPU spikes occur across multiple cores.
• One or more Content Management ID (CMID) processes repeatedly consume close to 100% CPU.
• Running CMID debug (for PROC in $(pidof cmid) ; do fw debug $PROC on TDERROR_ALL_ALL=5 ; done) shows these error messages:

[MAIN][rad_icap_client.cpp:44] ::rad_icap_clean_conn_map: [INFO] enter to ...
[MAIN][rad_icap_client.cpp:55] ::rad_icap_clean_conn_map: [ERROR] entry Key (session_id 337257) expired, removing key
[MAIN][rad_icap_client.cpp:59] ::rad_icap_clean_conn_map: [ERROR] Session id: 337257 TTL: 0
[MAIN][rad_icap_client.cpp:55] ::rad_icap_clean_conn_map: [ERROR] entry Key (session_id -280053504) expired, removing key

Cause

In a rare scenario, the CMID daemon can unexpectedly exit (without a core dump).

Solution

This problem was fixed. The fix is included in:

• Jumbo Hotfix Accumulator for R82.10 starting from Take 36
• Jumbo Hotfix Accumulator for R82 starting from Take 118
• Jumbo Hotfix Accumulator for R81.20 starting from Take 158

If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.

Hotfix installation instructions:

Refer to sk168597 - How to install a Hotfix.

NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Article Properties

Access Level: General
Status: Approved by TAC
Date Created: 2026-01-06
Last Modified: 2026-07-23