IBM Support

IBM Cloud Pak System - Virtual System Pattern Instance status is LAUNCHING due to compressed content under maestro directory

Troubleshooting


Problem

When restarting a Virtual System Pattern Instance, the instance remains in LAUNCHING state and middleware perspective shows 0 roles. 
CPU and Memory values for the Virtual Machine also report "unknown" values.

Cause

This problem symptom may occur for different reasons, but one situation which will cause this is compressed content (.gz) located under the /opt/IBM/maestro/agent/usr/servers/<Server_Name>/logs/ directory.
example:
/opt/IBM/maestro/agent/usr/servers/CustomNode.12342529101920/logs/trace.log.0.gz
IBM Cloud Pak System does not compress files located under this directory!  Instead,  a system or application administrator with access to the virtual machine might compress logs under the directory to try and free up or conserve disk space on the Virtual machine.
Compressing logs under IBM maestro agent directories is not supported and will prevent the IBM maestro agent from properly starting during a reboot of the Virtual Machine or restart of the Virtual System Pattern Instance.

 

Diagnosing The Problem

How to quickly check for compressed files..
syntax:
find /opt/IBM/maestro/agent/usr/servers/<Server_Name>/logs/ -name '*.gz'
example:
find /opt/IBM/maestro/agent/usr/servers/CustomNode.12342529101920/logs/ -name '*.gz'
The following error message will also be reported in the IBM maestro agent console log
/opt/IBM/maestro/agent/usr/servers/CustomNode.12342529101920/logs/console.log.0
[18/Sep/2017 11:58:35:317 -0500]  INFO CWWKA2412I: Using logging specification "*=info=enabled"
[18/Sep/2017 11:58:34:992 -0500]  AUDIT CWWKA0001A: Alpine launched.
[18/Sep/2017 11:58:37:173 -0500]  AUDIT CWWKA0002A: Kernel started after 2.181
Exception in thread "Alpine Feature update" 
java.lang.NumberFormatException: For input string: "gz"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:76)
at java.lang.Integer.parseInt(Integer.java:503)
at java.lang.Integer.<init>(Integer.java:688)
at com.ibm.ws.ras.internal.BaseTraceServiceWriter.openNewTraceFile(BaseTraceServiceWriter.java:491)
at com.ibm.ws.ras.internal.BaseTraceServiceWriter.getTraceFile(BaseTraceServiceWriter.java:791)
at com.ibm.ws.ras.internal.BaseTraceServiceWriter.traceToFile(BaseTraceServiceWriter.java:397)
at com.ibm.ws.ras.internal.BaseTraceService.trace(BaseTraceService.java:332)
at com.ibm.ws.ras.internal.BaseTraceService.trace(BaseTraceService.java:318)
at com.ibm.ws.ras.internal.BaseTraceService.audit(BaseTraceService.java:187)
at com.ibm.websphere.ras.Tr.audit(Tr.java:237)
at com.ibm.alpine.service.internal.TimestampImpl.auditStartTime(TimestampImpl.java:113)
at com.ibm.alpine.service.timestamp.TimestampUtil.auditStartTime(TimestampUtil.java:58)
at com.ibm.alpine.feature.internal.FeatureManager.updateFeatures(FeatureManager.java:317)
at com.ibm.alpine.feature.internal.FeatureManager.update(FeatureManager.java:281)
at com.ibm.alpine.feature.internal.FeatureManager$1.run(FeatureManager.java:254)
at java.lang.Thread.run(Thread.java:804)

Resolving The Problem

Uncompress the content and then restart the Virtual System Pattern Instance from the IBM Cloud Pak System UI
syntax:
gunzip -r /opt/IBM/maestro/agent/usr/servers/<Server_Name>/logs/ 
example:
gunzip -r /opt/IBM/maestro/agent/usr/servers/CustomNode.12342529101920/logs/

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":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Product Synonym

IPAS; PureApp; CPS

Document Information

Modified date:
26 August 2020

UID

ibm16323301