Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

IDS Replication has failed

Hello

The next saturday I had a replication problem with a server in a cluster. I dont konow exactly what was the reason of this failure. Somebody can help me ?

The logs in the server are these.

Jul 3 01:48:25, MX-BOS2-CCM05, Critical, Cisco Database Layer Monitor, : 0: Jul 03 06:48:25.156 UTC : %CCM_DB_LAYER-DB-2-IDSEngineCritical: Pay Attention. This alarm does not compromise data or prevent the use of the system. Event Class ID:mx_bos2_ccm05_ccm7_0_2_10000_18-7 Event class message:Dynamic Server Initialization failure. Event Specific Message: lization failure.:Checkpoint log record may not fit into the logical log buffer. Recommended minimum value for LOGBUFF is 34.:Ci Cluster ID:StandAloneCluster Node ID:MX-BOS2-CCM05, 2392

Jul 3 02:04:39, MX-BOS2-CCM05, Critical, Cisco Database Layer Monitor, : 1: Jul 03 07:04:39.719 UTC : %CCM_DB_LAYER-DB-2-IDSEngineCritical: Pay Attention. This alarm does not compromise data or prevent the use of the system. Event Class ID:mx_bos2_ccm05_ccm7_0_2_10000_18-7 Event class message:Dynamic Server Initialization failure. Event Specific Message: lization failure.:WARNING! Physical Log size 20000 is too small. Physical Log overflows may occur during peak activity Cluster ID:StandAloneCluster Node ID:MX-BOS2-CCM05, 2393

Jul 3 05:29:42, MX-BOS2-CCM05, Critical, Cisco Database Layer Monitor, : 229: Jul 03 10:29:42.407 UTC : %CCM_DB_LAYER-DB-2-IDSEngineCritical: Pay Attention. This alarm does not compromise data or prevent the use of the system. Event Class ID:mx_bos2_ccm05_ccm7_0_2_10000_18-6 Event class message:Internal Subsystem failure Event Specific Message: Subsystem failure: 'MT':Cannot fork CDRM_Refresher threadstart:mx_bos2_ccm05_ccm7_0_2_10000_18:ATTENTION:24:MT: cannot allocate Cluster ID:StandAloneCluster Node ID:MX-BOS2-CCM05, 2635

Jul 3 05:31:03, MX-BOS2-CCM05, Critical, Cisco Database Layer Monitor, : 403: Jul 03 10:31:03.414 UTC : %CCM_DB_LAYER-DB-2-IDSEngineCritical: Pay Attention. This alarm does not compromise data or prevent the use of the system. Event Class ID:mx_bos2_ccm05_ccm7_0_2_10000_18-24 Event class message:MT Event Specific Message: 8:ATTENTION:24:MT: cannot allocate memory :out of virtual shared memory :CiscoAlarmEnd Cluster ID:StandAloneCluster Node ID:MX-BOS2-CCM05, 2809

Jul 3 05:31:03, MX-BOS2-CCM05, Critical, Cisco Database Layer Monitor, : 404: Jul 03 10:31:03.624 UTC : %CCM_DB_LAYER-DB-2-IDSEngineCritical: Pay Attention. This alarm does not compromise data or prevent the use of the system. Event Class ID:mx_bos2_ccm05_ccm7_0_2_10000_18-6 Event class message:Internal Subsystem failure Event Specific Message: Subsystem failure: 'MT':Cannot allocate rstcb for CDRM_Refresher threadstart:mx_bos2_ccm05_ccm7_0_2_10000_18:ATTENTION:24:MT: ca Cluster ID:StandAloneCluster Node ID:MX-BOS2-CCM05, 2810

Jul 3 05:31:03, MX-BOS2-CCM05, Error, Cisco Database Layer Monitor, : 405: Jul 03 10:31:03.654 UTC : %CCM_DB_LAYER-DB-3-IDSReplicationFailure: Combined alarm for emergency and error situations. IDS Replication has failed Event Class ID: /var/log/active/cm/log/informix/ccm.log -31 Event class message:02 Cannot allocate rstcb for CDRM_Refresher thread 05 Event Specific Message: Temporary space ertmpsb is full. Invoking proactive procedure to avoid denial of service. It will take upto one hour to complete Cluster ID:StandAloneCluster Node ID:MX-BOS2-CCM05, 2811

Best regards

2 REPLIES
Green

Re: IDS Replication has failed

Thanks for the information,

Which version of CUCM and which platform you saw the error?

Is first time it happens?

For how many days server has been up?

As you highlighted it was an OOM error did you manage to get DB and Perfmon logs?

It may be a memory leak in IDS.DB processes or other processes which prevented replication jobs to execute (just a guess)

We may need to look at the logs, I suggest you open a TAC case to inesvtigate

Thanks

New Member

IDS Replication has failed

Hi!

I'm facing the same issue on one customer. They are running CUCM v7.0 which became End of Support.

Did you found any Bug ID related?

Thanks,

1729
Views
0
Helpful
2
Replies
CreatePlease to create content