Spectroserver crash on 10.4.1

Products

• CA Spectrum
• CA eHealth

Issue/Introduction

Spectrum Server crash on 10.4.1 on RHEL

Core indicates a crash caused the trap - They are using SNMPv3 profiles

Using host libthread_db library "/lib64/libthread_db.so.1". 
Core was generated by `/opt/spectrum/SS/SpectroSERVER'. 
Program terminated with signal 11, Segmentation fault. 
#0 0x00007f86eac4cf8f in __strlen_sse42 () from /lib64/libc.so.6 
#0 0x00007f86eac4cf8f in __strlen_sse42 () from /lib64/libc.so.6 
#1 0x00007f86eb6c76c5 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(char const*, std::allocator<char> const&) () from /lib64/libstdc++.so.6 
#2 0x00007f86f0f0b6df in CsHPSETrapReceiver::DoTask() () from /opt/SPECTRUM/lib/../SS/libhpse.so.1 
#3 0x00007f86f0f098b6 in CsHPSETask::threadRun(void*) () from /opt/SPECTRUM/lib/../SS/libhpse.so.1 
#4 0x00007f86eaedbdd5 in start_thread () from /lib64/libpthread.so.0 
#5 0x00007f86eac04ead in clone () from /lib64/libc.so.6

Cause

• Engineering suspect that the crash could be because of stack corruption which happens very rare on customer environment.

Environment

Release : 10.4.1

Component : Spectrum Core / SpectroSERVER

Resolution

From Engineering:

Customer provided call stack as follows:

#0  0x00007f86eac4cf8f in __strlen_sse42 () from /lib64/libc.so.6
#0  0x00007f86eac4cf8f in __strlen_sse42 () from /lib64/libc.so.6
#1  0x00007f86eb6c76c5 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(char const*, std::allocator<char> const&) ()
   from /lib64/libstdc++.so.6
#2  0x00007f86f0f0b6df in CsHPSETrapReceiver::DoTask() () from /opt/SPECTRUM/lib/../SS/libhpse.so.1
#3  0x00007f86f0f098b6 in CsHPSETask::threadRun(void*) () from /opt/SPECTRUM/lib/../SS/libhpse.so.1
#4  0x00007f86eaedbdd5 in start_thread () from /lib64/libpthread.so.0
#5  0x00007f86eac04ead in clone () from /lib64/libc.so.6

This is resolved in DX NetOps Spectrum 10.4.2 and above to apply the following fix:

 

Symptom:

 Creation and saving of V3 management profiles was making SpectroSERVER unresponsive.

Resolution: The issue has been resolved. Now, the engineID is not updated for 127.0.0.1. (DE449679, 31697282, 10.4.2)