ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

The SpectroSERVER crashed after upgrading to Spectrum 10.4.2.0 on Linux

book

Article ID: 200749

calendar_today

Updated On:

Products

CA Spectrum CA eHealth

Issue/Introduction

The SpectroSERVER crashed after upgrading  to Spectrum 10.4.2.0 on Linux. The following is the stack trace from the core file:

(gdb) where
#0  0x00007fb7dac40623 in CsGHashTable::add(void*, int) () from /opt/SPECTRUM/lib/libGlobl.so.1
#1  0x00007fb7ddaa97f7 in CsConnNotifyTable::add(CsConnNotifyReg*) () from /opt/SPECTRUM/lib/libgserv.so.1
#2  0x00007fb7ddaf3b60 in CsServiceConn::reg_connect_event(void (*)(void*, CsError::CsError_e, CsServiceConn const*), void*) () from /opt/SPECTRUM/lib/libgserv.so.1
#3  0x00007fb7ddaa7427 in ConnectionMonitoringInfo::tryRegister(CsLscpeHandle const&, void (*)(void*, CsError::CsError_e, CsServiceConn const*)) () from /opt/SPECTRUM/lib/libgserv.so.1
#4  0x00007fb7ddb052f7 in LandscapeConnectionMonitor::registerForConnectionChanges(CsLscpeHandle const&, CsLscpeHandle const&, CsLscpeHandle const&, CsLscpeHandle const&, ConnectionMonitoringInfo::ConnectionRegistrationType_e, void (*)(void*, CsError::CsError_e, ConnectionChangeInfo const&), void*, unsigned int, bool, bool, ConnectionCallbackInfo*) ()
   from /opt/SPECTRUM/lib/libgserv.so.1
#5  0x00007fb7ddb054df in LandscapeConnectionMonitor::registerForConnect(CsLscpeHandle const&, RemoteConnectionMonitorInfo const&) () from /opt/SPECTRUM/lib/libgserv.so.1
#6  0x00007fb7ddabca8c in CsDLscpeIf::reg_connect(RemoteConnectionMonitorInfo const*) () from /opt/SPECTRUM/lib/libgserv.so.1
#7  0x00007fb7ddabcdfb in CsDLscpeIf::dispatch(CsVnmMsg*, CsVPConnHandle const&, CsSecurityIf const*) () from /opt/SPECTRUM/lib/libgserv.so.1
#8  0x00007fb7ddaebc69 in CsSecureConn::dispatch_on_behalf(CsVnmMsg*, CsVPConnHandle const&, CsSecurityIf const*) () from /opt/SPECTRUM/lib/libgserv.so.1
#9  0x00007fb7ddb00a44 in CsVnmConnect::dispatch(CsVnmMsg*) () from /opt/SPECTRUM/lib/libgserv.so.1
#10 0x00007fb7ddaeb0ed in CsRequestMgr::process_work_node(CsWorkNode*) () from /opt/SPECTRUM/lib/libgserv.so.1
#11 0x00007fb7dd842a70 in CsWorkScheduler::do_work() () from /opt/SPECTRUM/lib/libwkmgr.so.1
#12 0x00007fb7e2584211 in moot_thread_start () from /opt/SPECTRUM/lib/libmoot.so.1
#13 0x00007fb7d6601010 in ?? () from /lib64/libc.so.6
#14 0x0000000000000000 in ?? ()

Cause

The root cause of the issue is specific to the corruption using the SpectroSERVER_noMTS binary.

Environment

Release : 20.2 running on Linux

Component : Spectrum Core / SpectroSERVER

Resolution

This issue can be addressed by copying the $SPECROOT/SS/support/SpectroSERVER_mts binary to the $SPECROOT/SS directory and then renaming it to SpectroSERVER.