The problem sounds familiar; I saw it with a customer some time ago. I remember that it had something to do with confd.
We then did things like running “show configuration” in debug mode.
clish -d 4 -c "show configuration"
Where 4 is the highest debug level.
Then I remember the analysis of confd as described in processes and daemons.
First, as indicated below, search in /var/log/messages for routed and confd search pattern.
Then to restart confd using tellpm process:confd t
Unfortunately, that's all I can remember, and it was also an older version and may not even be suitable for this use case, but maybe it will help at least a little.
sk97638 - Check Point Processes and Daemons
|
confd
|
Description
|
Database and configuration.
|
|
Path
|
/bin/confd
|
|
Important Note
|
Maintenance window is required to restart this daemon:
- When
confd daemon is starting, by design, it restarts any currently running routed daemons (by sending a TERM signal). It is done to avoid possible issues in Gaia Clish (e.g., returning invalid results for routing-related commands like "show route").
- Since
routed daemon is responsible for all the routing in Gaia OS, short traffic outage will occur while routed daemon is being restarted.
- Since
routed daemon is a Critical Device in Check Point cluster (since R76), cluster fail-over might occur while routed daemon is being restarted (refer to sk92878).
- In a VSX environment, restarting the routed process owned by VS0 restarts routed for all Virtual Systems. Contact Check Point support for assistance.
|
|
Log File
|
/var/log/messages
|
|
To Stop
|
tellpm process:confd
|
|
To Start
|
tellpm process:confd t
|
|
Debug
|
Examine /var/log/messages
|
and now to something completely different - CCVS, CCAS, CCTE, CCCS, CCSM elite