IBM Support

Script Execution fails with no trace file at deployment time but deployment remains Running

Troubleshooting


Problem

The problem is identified in the folder/file limit that is set to default with 65K for drouter rainmaker directory. Cloud Pak System fails to create a new folder and file in /drouter/ramdisk2/mnt/raid-volume/raid0/rainmaker-scripts-logs/ directory with exception as directory not found.
Cloud Pak System is set with default security configuration of a limit of 65K count. Post the limit, deployment starts seeing the behavior as mentioned in the "Symptom" section.

Symptom

After the count reaches the limit, you can observe the following behavior:
Existing deployment will see no trace file for script execution.
A new deployment will succeed with script execution failure.

Diagnosing The Problem

Check the Workload logs for the following script execution failure:

error.log:[2020-11-19 07:20:49:392 UTC] 00038500 groovy        E app.scripts.groovy.rainmaker.scripts.ScriptsExecutedHandler.groovy run java.io.IOException: No such file or directory

The exception seen on this trace clearly states that the error is due to "File not found".

Resolving The Problem

To resolve the problem, the following actions can be taken:

1. Take a back up of logs folder (/drouter/ramdisk2/mnt/raid-volume/raid0/rainmaker-scripts-logs/) and clean the logs directory to reduce the count of file/folder.
2. PSM reset Service60. It helps to reduce the count in log directory.

Document Location

Worldwide

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSJNNT","label":"IBM Cloud Pak System Software Suite"},"ARM Category":[{"code":"a8m0z000000cwm2AAA","label":"Product Components"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
03 December 2020

UID

ibm16373956