SMARTS services do not start after upgrading

Products

• Network Observability
• VMware Smart Assurance

Issue/Introduction

After upgrading NetOps SMARTS there were services that stayed in the NOT-RUNNING state.  When reviewing the log file there is a stack trace and you can see the service crashed.

When running sm_service show not all services were running.

Cause

Use of SM_USE_SAM_CORE=1 entry in a non SAM domain runcmd_env.sh file

Resolution

The SM_USE_SAM_CORE= entry is supported for SAM domain only.

 

Edit the runcmd_env.sh for the non SAM domain (for example, IP, VoIP etc) and remove the following entry:

SM_USE_SAM_CORE=1

For example, edit the /opt/InCharge/IP/smarts/local/conf/runcmd_env.sh file and if you have "SM_USE_SAM_CORE=" delete it:

SM_BROKER_DEFAULT=localhost:426
SM_LICENSE=null
SM_SNMP_BUG_COMPATIBLE=TRUE
SM_INCOMING_PROTOCOL=1,0
SM_OUTGOING_PROTOCOL=1,0
SM_IP_VERSIONS=v6v4
SM_LOCALE=en_US
SM_ENCODING_OUTPUT=UTF-8
SM_GUI_DISPLAYNAME_CLASSES=CORE_Collection
SM_DEFHOME=/dev/null
SM_FIPS140=FALSE
SM_USE_SAM_CORE=1
SM_LOG_ROLL_SIZE=200M
SM_BACKUP_FILE_LIMIT=5
SM_ALLOW_LEGACY_CRYPTO=TRUE
SM_TLS_MIN_VERSION=1.2
SM_TLS_MAX_VERSION=1.3

After you have deleted SM_USE_SAM_CORE=1 save the file and start the service(s) that crashed.  For example:

sm_service start ic-am-pm-server