This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
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?
------- If you like this post please give a thumbs up(kudo)! 🙂
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.
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:
Stop the Check Point services:
cpstop
Remove the problematic CPEPS tables:
cd $CPDIR/database/cpeps
mkdir /var/cpeps
mv CPEPS* /var/cpeps
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.
