01-29-2016 02:47 PM - edited 03-19-2019 10:40 AM
About every hour we are getting a Core Dump alert from RTMT on our CUC Publisher. I have included the backtrace below. Has anyone seen this kind of error on Unity Connect 10.5?
====================================
backtrace - CUCM
===================================
#0 0x00a578f8 in fork () from /lib/libc.so.6
#1 0x00a1877e in _IO_proc_open@@GLIBC_2.1 () from /lib/libc.so.6
#2 0x00a18a9a in popen@@GLIBC_2.1 () from /lib/libc.so.6
#3 0x08053465 in GetDuplexSettings () at cdpd.c:1852
#4 0x080537e0 in cdpd_read_cache () at cdpd.c:264
#5 0x08053d21 in cdp_readcachedump_timed_out (threadid=0x0) at cdpd.c:169
#6 0x004f6b39 in start_thread () from /lib/libpthread.so.0
#7 0x00a98c2e in clone () from /lib/libc.so.6
====================================
info registers
====================================
eax 0x106f48f0 275728624
ecx 0xb48ff4 11833332
edx 0xf74efbe0 -145818656
ebx 0xb48ff4 11833332
esp 0xf74ed2c4 0xf74ed2c4
ebp 0xf74ed318 0xf74ed318
esi 0x106f48f0 275728624
edi 0xe07000 14708736
eip 0xa578f8 0xa578f8 <fork+312>
eflags 0x10206 [ PF IF RF ]
cs 0x23 35
ss 0x2b 43
ds 0x2b 43
es 0x2b 43
fs 0x0 0
gs 0x63 99
====================================
info threads
====================================
* 1 Thread 0xf74efb70 (LWP 1461) 0x00a578f8 in fork () from /lib/libc.so.6
Thanks in advance...
01-29-2016 09:09 PM
Couldn't find any relevant defect with this, try contacting TAC with below detail for analysis on the same
utils core active list
utils diagnose test
show status
show hardware
CCM trace, RisDC perfmon logs and app/sys logs for the problematic time stamp.
02-01-2016 06:33 AM
Thanks for the reply...
I didn't see any defects either but thought I would ask the question here in case I missed something. As you suggest, I have opened a support case with TAC.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide