search cancel

SpectroSERVER crashing converting attribute values

book

Article ID: 189476

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

SpectroSERVER crashing converting attribute values. The following is seen in the stack trace of the core file:

#0  0x0000003a9407b710 in ?? ()
#1  0x00002b1260606035 in CsBuffer::makestr(int, char) const () from /opt/SPECTRUM/lib/libGlobl.so.1
#2  0x00002b125d2a44a0 in CsAttrConvert::set_attr_value(CsCAttribute::CsCValue&, CsAttrDesc::CsAttrType_e, void const*) ()
   from /opt/SPECTRUM/lib/libssorbconvert.so.1
#3  0x00002b125d2a4bde in CsAttrConvert::make_CsCValue(void const*, CsAttrDesc::CsAttrType_e, CsCAttribute::CsCValue*) () from /opt/SPECTRUM/lib/libssorbconvert.so.1
#4  0x00002b125d2a5459 in CsAttrConvert::make_CsCAttrValue(CsAttrValRsp const&, CsCAttribute::CsCAttrValue*) () from /opt/SPECTRUM/lib/libssorbconvert.so.1
#5  0x00002b125d2a5516 in CsAttrConvert::make_CsCAttrValList(CsAttrValRspList const&, CsCAttribute::CsCAttrValList*) () from /opt/SPECTRUM/lib/libssorbconvert.so.1
#6  0x00002b125d2ac542 in CsModelConvert::make_CsCModelAttrValList(CsModelAction const&, CsCModelDomain::CsCModelAttrValList*) ()
   from /opt/SPECTRUM/lib/libssorbconvert.so.1
#7  0x00002b125d2ac5f6 in CsModelConvert::make_CsCAttrValListOfModels(CsModelActionList const&) () from /opt/SPECTRUM/lib/libssorbconvert.so.1

Cause

Spectrum having an issue with non-ascii characters

Environment

Release : Any

Component : Spectrum Core / SpectroSERVER

Resolution

Use the following to look for non-ascii characters and correct:

1. Run the Modeling Gateway export

    a. Log into the SpectroSERVER system as the user that owns the Spectrum installation

    b. If on Windows, start a bash shell by running "bash -login"

    c. cd to the $SPECROOT/SS-Tools directory and enter the following command where <VNM> is the hostname of the SpectroSERVER system:

./modelinggateway -vnm <VNM> -e MG_Export

2. Review the MG_Export.xml file for any non-ascii characters.

NOTE: A couple of non-ascii characters known to cause this issue are "ñ" and "ö"

Additional Information

If you are not sure, you can use the regular expression "[^\x00-\x7F]+" to look for non-ascii characters in the MG_Export.xml file.

For example:

1. Go to https://regex101.com/

2. Enter [^\x00-\x7F]+ in the REGULAR EXPRESSION field

3. Enter your text string from the MG_Export.xml file in the "TEST STRING" field

4. Matches will be displayed in the MATCH INFORMATION field