CPD crashed/terminated without a Core Dump or the process is consuming high CPU utilization

[AkosBakos]

Hi All,

I am facing with this issue:

[ERROR] CPD (pid_of_cpd) did not send keep-alive message for x number of times

https://support.checkpoint.com/results/sk/sk101484

on a VSX environment.

The cpwd.elg exist only on the vs0, however the issue arose in one of the VSs.

Do I need to move the files in VS0, or the affected VS too?

Akos

[Lesley]

Both SK's below states you have to go the correct vs and not vs0

https://support.checkpoint.com/results/sk/sk109940

https://support.checkpoint.com/results/sk/sk98013

Although the versions are bit older i still think they are relevant for this question

For de CPD issue. I have seen this issue in an older take, get's solved in higher take and then got introduced again in a newer take. What take you are running? 

[AkosBakos]

Yes it is older one (R81.10 something) , and the upgrade planning  is in progress, but you know how it works… 

things always happen in the worst moment…

A

[Lesley]

If it is old take and known CPD bug issue reboot is most quick way. After long period time it will come back but in meantime you can plan upgrade. 

[Duane_Toler]

This was a known issue not too long ago, at least on the management servers.  I posted a script in the Check Mates Toolbox a while back that you can run as a scheduled job.

https://community.checkpoint.com/t5/Scripts/Restart-CPD-script/m-p/217862#M1159

This may help you until you get a recent Jumbo HFA on it.

[AkosBakos]

THX!

[the_rock]

Hopefully upgrade to R81.20 should fix it...

Andy

[the_rock]

Hey brother,

AI copilot gives something similar, but take it for what its worth 🙂

Andy

************

It seems that the CPD (Check Point Daemon) process on your gateway is experiencing issues, as indicated by the error message[ERROR] CPD (pid_of_cpd) did not send keep-alive message for x number of times. This can lead to problems with SIC communication and policy installation.

Here are the steps to resolve this issue:

1. Stop the Check Point services:

   cpstop
   

2. Remove the problematic CPEPS tables:

   cd $CPDIR/database/cpeps
   mkdir /var/cpeps
   mv CPEPS* /var/cpeps
   

3. Start the Check Point services:

   cpstart
   

The CPEPS tables will be recreated after CPD starts.

Note: If you are using Maestro blades, the changes must be implemented on all SGMs and require a reboot.

If the issue persists, it is recommended to contact Check Point Support for further assistance. They may need to runstraceon$CPDIR/bin/cpdto confirm the cause of the high CPU utilization or other underlying issues.

BE AWARE

Important - To prevent negative impact on your production environment, double-check the provided information in the Administration Guide for the involved product.

Learn more:

1. sk101484 - CPD crashed/terminated without a Core Dump or the process is consuming high CPU utilizati...
2. sk182218 - CPD daemon constantly stops working in a Maestro Security Group
3. sk116861 - Policy installation fails with "SIC General Failure [ SIC error no. 148 ]" error
4. sk182370 - Multi-Domain Management Server or Security Management Server do not respond because of a ...
5. sk86320 - How to debug the CPD daemon
6. sk135492 - "Installation failed. Reason: Authentication error [ SIC error no. 147]" error message, p...
7. sk111944 - "URL Filtering / Application control is not responding" message in SmartView Monitor