A fix is available
APAR status
Closed as program error.
Error description
During deployment, patterns that have deployed successfully in the past will fail on different, random script packages. The "Current status" of the deployment will read: The required initialization script package xxxxxx failed to execute successfully on virtual machine yyyyyy More than one script package may fail in this way, including the 'maestro' and 'Must Gather Logs' packages, as well as custom script packages in the pattern. Customers may also see poor performance in the user interface when using the Workload Console panels. The deployments may take longer than normal to complete, or end with an error status. In the "Log Viewer" interface for an impacted VM, clicking to expand the file directory tree in the left hand navigator may cause a pop up message of "Service not available. An error occurred when listing the log file. Check the server log for details." In the workload log (trace.log), multiple, frequent CTGRI0031E and CTGRI0081E Errors will be seen: java.net.ConnectException: CTGRI0031E Could not fully initialize the Unix environment on the target java.net.ConnectException: CTGRI0081E RXA internal command run on <IP address> could not be completed during the specified timeout interval.
Local fix
The following steps temporarily interrupt access to the Workload Console panels. All running workloads will continue to function without interruption. . The issue may be addressed by the following commands to restart the Workload Console (IWD) process: . 1) Verify that no deployments are in process. Wait for any in progress deployments to get to a final status before proceeding. Warn users not to start any further deployments until given confirmation that the system is ready. . 2) Using an ID that has full hardware administration permissions, open a Secure Shell(SSH) connection to the PureSystems Manager . See the section "Starting the PureApplication System Administrative Interface" in the Knowledge Center for additional information . http://www.ibm.com/support/knowledgecenter/SSCRSX_2.0.0/doc/c lihelp/appsysadmincli-start.dita . 3) In the PSM command line session, issue the following command: . psm info all . and verify that "High Availability Status" is "Online" and all Services show "Online" status. . 4) Next, issue the following command: . psm reset service10 . 5) Use the command . psm info all . to watch for service 10 (IWD) to be back to running/online status and for the "High Availability Status" to also return to "Online". This should take approximately 10 - 15 minutes. You will need to reissue the command periodically to see any change in status. . 6) Exit the PSM SSH session and disable the PSM shell account on the Troubleshooting page. . 7) Confirm with users that deployments are working normally. . If you experienced sluggish performance in the Workload Console panels, you should see much faster responses for page actions.
Problem summary
Connection errors during script packages running on virtual systems can cause a Java virtual machine thread leak that may cause deployment failure or slow deployments.
Problem conclusion
A code fix is being provided in PureApplication System version 2.0.0.1 interim fix 1, and higher versions, that handles connection objects when exceptions occur and prevents the Java thread leak.
Temporary fix
Comments
APAR Information
APAR number
IT05824
Reported component name
PAPP SYS 8382 I
Reported component ID
5725G3200
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-11-28
Closed date
2015-01-28
Last modified date
2015-03-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
PAPP SYS 8382 I
Fixed component ID
5725G3200
Applicable component levels
R200 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSM8NY","label":"PureApplication System"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"200","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
17 March 2015