IBM Support

Shared Services System Monitoring instance update to 1.0.19.0 might not start successfully upon instance stop and start in IBM Cloud Pak System

Troubleshooting


Problem

In IBM Cloud Pak® System, the Shared Services > System Monitoring instance might go into an Error state after you stop and start the instance upon an update to 1.0.19.0.
This problem is observed in IBM Cloud Pak® System 2.3.3.3.

Symptom

The steps that result into an Error status for the Shared Services > System Monitoring instance are as follows:
– The System Monitoring instance was updated to 1.0.19.0 from 1.0.18.0 or earlier and the instance was in Running state.
– The instance was stopped and started.
– The instance might go into Error state.

Environment

Virtual machine:
Log in to the Hub-TEMS virtual machine and verify that the agents are not running. Use the following command:
/opt/IBM/ITMSS/bin/cinfo -r

User interface:
On the Shared Services > System Monitoring instance page, the instance status is displayed as Error.
 

Diagnosing The Problem

Logs:
The following message appears in the trace.log file under ITM-Hub-TEMS.* -> IWD Agent -> .../logs/ITM-Hub-TEMS.*.Hub-TEMS/.
The log location on Hub-TEMS virtual machine is:
/opt/IBM/maestro/agent/usr/servers/ITM-Hub-TEMS.*/logs/ITM-HubTEMS.*.Hub-TEMS/trace.log*

Error running updateSituations.sh. RC = 99

Document Location

Worldwide

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFQSV","label":"IBM Cloud Pak System Software"},"ARM Category":[{"code":"a8m0z000000cwm2AAA","label":"Product Components"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"2.3.3"}]

Document Information

Modified date:
06 August 2021

UID

ibm16473105