CUCM 14.0.1 - RTMT CDP Alerts

[Quintin.Mayo]

Hi,

We received the below CDP service alerts but I'm unable to find any information thus far for why the service fails.  Is this something we should be concerned and need to take some action on? Any direction would be greatly appreciated. Thanks.

At Thu May 25 00:00:45 EDT 2023 on node 10.111.240.110, the following SyslogSeverityMatchFound events generated:
SeverityMatch : Critical
MatchedEvent : May 25 00:00:29 cmpub local4 2 : 1056: cmpub.csd: May 25 2023 04:00:29.638 UTC : %UC_SERVICEMANAGER-2-ServiceFailed: %[ServiceName=Cisco CDP][Reason=Service stopped abruptly][AppID=Cisco Service Manager][ClusterID=][NodeID=cmpub]: Service terminated.
AppID : Cisco Syslog Agent
ClusterID :
NodeID : cmpub
TimeStamp : Thu May 25 00:00:29 EDT 2023

SeverityMatch : Critical
MatchedEvent : May 25 00:00:29 cmpub local7 2 : 1056: cmpub.csd: May 25 2023 04:00:29.638 UTC : %UC_SERVICEMANAGER-2-ServiceFailed: %[ServiceName=Cisco CDP][Reason=Service stopped abruptly][AppID=Cisco Service Manager][ClusterID=][NodeID=cmpub]: Service terminated.
AppID : Cisco Syslog Agent
ClusterID :
NodeID : cmpub
TimeStamp : Thu May 25 00:00:30 EDT 2023

At Thu May 25 00:00:45 EDT 2023 on node , the following CoreDumpFileFound events generated:
TotalCoresFound : 1
CoreDetails : The following lists up to 6 cores dumped by corresponding applications.
Core1 : Cisco CDP (core.7959.6.cdpd.1684987219)
AppID : Cisco Log Partition Monitoring Tool
ClusterID :
NodeID : cmpub
TimeStamp : Thu May 25 00:00:21 EDT 2023

[Quintin.Mayo]

Below is the backtrace information any direction or input would be appreciated.

admin:utils core active analyze core.7959.6.cdpd.1684987219

This command may use a considerable amount of I/O
and running it may impact system performance.

It is highly recommended that this command be
run off-hours.

Continue (y/n)?y
Reading symbols from /usr/local/cm/bin/cdpd...done.
[New LWP 7959]
[New LWP 7997]
[New LWP 14061]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/local/cm/bin/cdpd -f'.
Program terminated with signal 6, Aborted.
#0 0xf76dd430 in __kernel_vsyscall ()

====================================
backtrace - CUCM
===================================
#0 0xf76dd430 in __kernel_vsyscall ()
#1 0xf69a32a7 in raise () from /usr/lib/libc.so.6
#2 0xf69a4ae3 in abort () from /usr/lib/libc.so.6
#3 0xf69e5025 in __libc_message () from /usr/lib/libc.so.6
#4 0xf6a8bff5 in __fortify_fail () from /usr/lib/libc.so.6
#5 0xf6a8a00a in __chk_fail () from /usr/lib/libc.so.6
#6 0xf6a8bf0a in __fdelt_warn () from /usr/lib/libc.so.6
#7 0x56584574 in main (argc=2, argv=0xff9428b4) at cdpd.c:1467
====================================
info registers
====================================
eax 0x0 0
ecx 0x1f17 7959
edx 0x6 6
ebx 0x1f17 7959
esp 0xff93f2c4 0xff93f2c4
ebp 0xff93fa48 0xff93fa48
esi 0x739 1849
edi 0xf6b3b000 -155996160
eip 0xf76dd430 0xf76dd430 <__kernel_vsyscall+16>
eflags 0x246 [ PF ZF IF ]
cs 0x23 35
ss 0x2b 43
ds 0x2b 43
es 0x2b 43
fs 0x0 0
gs 0x63 99
====================================
info threads
====================================
Id Target Id Frame
3 Thread 0xf5bffb40 (LWP 14061) 0xf76dd430 in __kernel_vsyscall ()
2 Thread 0xf65eab40 (LWP 7997) 0xf76dd430 in __kernel_vsyscall ()
* 1 Thread 0xf691d740 (LWP 7959) 0xf76dd430 in __kernel_vsyscall ()