Cisco Bug: CSCuq78452 - XCP router core coincides with Informix error -144
Sep 26, 2014
- Cisco Unified Communications Manager IM & Presence Service
- Cisco Unified Communications Manager IM and Presence Service Version 9.1
Known Affected Releases
Symptom: XCP router service cored. Core backtrace shows the following: Program terminated with signal 11, Segmentation fault. #0 js_init_filtered_session_list (user=0xa04fe70, jp=0xae663d30) at src/components/jabber2/jsm/sessions.c:1919 in src/components/jabber2/jsm/sessions.c Thread 1 (Thread 0xaf057b90 (LWP 22616)): #0 js_init_filtered_session_list (user=0xa04fe70, jp=0xae663d30) at src/components/jabber2/jsm/sessions.c:1919 #1 0x00b238d3 in _js_deliver_local_user (user=0xa04fe70, p=0xae663d30) at src/components/jabber2/jsm/jsm_deliver.c:396 #2 0x00b23b3f in _e_send_cb (handled=0, m=0xafb31a20, arg=0x0) at src/components/jabber2/jsm/jsm_deliver.c:1851 #3 0x00b27b43 in _js_mapi_call_mtq_cb (arg=0xafb31a20) at src/components/jabber2/jsm/modules.c:288 #4 0x0060a9da in _mtq_worker_thread_func (arg=0xaf409578) at src/libs/libjcore/src/jabber/mtq.c:190 #5 0x0011d6e1 in start_thread () from /lib/libpthread.so.0 #6 0x0092cd3e in clone () from /lib/libc.so.6 At the time when the service cored, there is an Informix error thrown on rosters update, as can be seen in XCP router logs: 11:40:36.816 |af67fb90| error| Default update rosters set state = ?, contact_jid = ?, nickname = ?, sub_reason = ? where user_id = ? and roster_id = ? 11:40:36.817 |af67fb90| error| Default IdsODBC::logErrors: DB Error Report - SQLError: -1 11:40:36.817 |af67fb90| error| Default IdsODBC::logErrors: DB Error record 1 (Native error: -211, ISAM error -144, SQLSTATE: S1000) [Informix][Informix ODBC Driver][Informix]Cannot read system catalog (sysprocplan). 11:40:36.817 |af67fb90| error| Default IdsODBC::logErrors: End of DB error report 11:40:36.817 |af67fb90| error| Default failed SQL operation update rosters set state = ?, contact_jid = ?, nickname = ?, sub_reason = ? where user_id = ? and roster_id = ? Conditions: CUP version 184.108.40.206900-1 We don't know under which circumstances this issue happened, so we couldn't reproduce it. No errors observed in database logs (ccm and dbmon) and no high memory usage noticed. Core backtrace and logs attached.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases