Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

CPSEMD process in a loop after upgrade from R80.10 to R80.30

Hello everybody,

We are comming from R80.10 standalone console with SmartEvent integrated solution where everything works perfectly.

Now after upgrade to R80.30 (new VM and import config) We are suffering a loop in CPSEMD process: during 10 times its try to unsucessfully start and then the count is reset to "0" and Terminated (After a while the loop start again)

CPSEMD  27446    E  8    [08:47:28] 5/10/2020   N    cpsemd

While the loop is running is not possible access to smartdashboard because a timeout, and the API doesnt work either, when the loop is NOT running everything works fine as far I know.

There is a case opened with checkpoint but after a month they still dont know what is the root issue, the only solution we are tried is increase the DB max size.

cpsemd.elg show always the same loop messages fails:

[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:47:29] CPSEMD: Mon Oct 5 08:47:29 2020

[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:48:04] CDBConnection::connect2Server: Connection cannot be initiated. Please make sure that 'localhost' is up and running and correctly defined. fwm may still be initializing.
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:48:04] Error: Failed to connect to CPMI locally in try number #1. FWM is probably still initializing. Will try again in 10 seconds.
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:48:49] CDBConnection::connect2Server: Connection cannot be initiated. Please make sure that 'localhost' is up and running and correctly defined. fwm may still be initializing.
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:48:49] Error: Failed to connect to CPMI locally in try number #2. FWM is probably still initializing. Will try again in 10 seconds.
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:49:37] CActiveMQClient::initConnection: before connection start, if stuck check ssl parameters.
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:49:37] CActiveMQClient::initConnection: Connection initiated successfully.
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:49:39] No resolving for objects will be done. In order to enable this kind of resolving, please change the registry ResolveObjects to be 1.
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:49:39] No DNS resolving will be done. In order to enable this kind of resolving, please change the registry ResolveDNS to be 1.
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:49:39] CSeamApplication::_UpdateDefinedCorrUnit: Error getting correlation units set: Operation not permitted
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:49:43] CDBConfiguration::RefreshStatus() - Failed to calculate available DB max size.
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:49:43] registry value for "HandleIPSFollowUp" is =0 then no ips follow up handling will be performed
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:49:43] registry value for "HandleDLPFollowUp" is =0 then no dlp follow up handling will be performed
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:49:50] CSeamApplication::msg_cb: FAILED to connect to messaging server
[CPSEMD 27446 4060125184]@GESN01[5 Oct 8:49:50] CSeamApplication::msg_cb: disconnected
[CPSEMD 27446 3838835520]@GESN01[5 Oct 8:51:49] Warning:cp_timed_blocker_handler: A handler [0x82289f0] blocked for 119 seconds.
[CPSEMD 27446 3838835520]@GESN01[5 Oct 8:51:49] Warning:cp_timed_blocker_handler: Handler info: Library [cpsemd], Function offset [0x1e09f0].
[CPSEMD 27446 3838835520]@GESN01[5 Oct 8:51:49] Warning:cp_timed_blocker_handler: Handler info: Nearest symbol name [_ZN23CAutomaticPolicyBuilder33__sched_SchedListenToNotificationEPv], offset [0x1e09f0].
[CPSEMD 2072 4061050880]@GESN01[5 Oct 8:55:29] CPSEMD: Mon Oct 5 08:55:29 2020

 

Thanks in advance,

 

 

0 Kudos
Reply
2 Replies
Highlighted

For everyones wants to know, checkpoint support was able to solvent the issue.

It was a sync problem between FWM and CPSEMD which caused crash in the processes, they don´t have any issue like this before so they late a little in found the solution.

 

regards!

0 Kudos
Reply
Highlighted
Employee
Employee

Do you know what was the case number you raised with TAC so we can reference that fix?

0 Kudos
Reply