Scribd
Upload
17 views2 pages

3PAR File Persona - A Crash in Var-Log-Java Was Detected.

The document addresses a crash detected in the HPE 3PAR File Persona due to low Java heap space. It provides a resolution by increasing the allocated memory for the JVM from 256 MB to 320 MB through specific steps. The article is confidential and intended for internal use only, detailing procedures for HPE personnel to resolve the issue.

Uploaded by

Mike Ac
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
17 views2 pages

3PAR File Persona - A Crash in Var-Log-Java Was Detected.

The document addresses a crash detected in the HPE 3PAR File Persona due to low Java heap space. It provides a resolution by increasing the allocated memory for the JVM from 256 MB to 320 MB through specific steps. The article is confidential and intended for internal use only, detailing procedures for HPE personnel to resolve the issue.

Uploaded by

Mike Ac
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

HPE Knowledge Article

3PAR File Persona - A crash in /var/log/java was detected.

Article Number mmr_sf-EN_US000018727

Environment

HPE 3PAR StoreServ 8200 2-node Field Integrated Storage Base


3.2.2.390(MU2);P11,P1264,P15,P19,P20

Issue

Message : File Services Node:0:node1fs Failed (DOWN)


Details : A crash in /var/log/java was detected. Requesting a new automatic collection.

Cause

Java heap space too low

Resolution
Essentially, we can just boost the amount of memory allocated to the JVM and it should be enough to effectively work around the
issue.

Please follow the steps outlined below to do that:


**** Do not send this to a customer as it requires access to the fsnodes which they don't have. ****

On all file service nodes, logon as root:

1. Create a backup of the JVM launcher properties file.


a. # mkdir -p /local/HP/backup

b.# cp -p /etc/infrmanconfig/launcher.properties /local/HP/backup/launcher.properties_`date "+%m%d%Y_%H%M"`

c. # diff /etc/infrmanconfig/launcher.properties /local/HP/backup/launcher.properties*

2. With editor of preference, modify /etc/infrmanconfig/launcher.properties


to increase JVM memory size from 256 MB to 320 MB.
# vim /etc/infrmanconfig/launcher.properties
Change:
MEMORY_ARGS="-Xmx256m -Xms64m -XX:ErrorFile=/var/log/java/hs_err_pid%p.log -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/var/log/java"
to:
MEMORY_ARGS="-Xmx320m -Xms64m -XX:ErrorFile=/var/log/java/hs_err_pid%p.log -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/var/log/java"

3. Compare modified launcher.properties to original and ensure only the one change has been made.
# diff /etc/infrmanconfig/launcher.properties /local/HP/backup/launcher.properties*

4. Restart the PML instance.


a. Disable PM failover.
# pm_server_config -m nopmfailover -A
# pm_server_config -i

b. Restart the service.


# pm_plugin -H (verify plugin states)

send a message notifying that you are restarting the pml.


# logger "PML restarted by HPE to increase memory heap"

# /usr/local/pml/init/infrastructure_server restart

# pm_plugin -H (verify plugin states, may take several minutes to recover plugins)

c. Display status
# pm_server_config -i

d. make non-pml nodes passive again


# pm_server_config -m passive -A

Internal Notes

NOTICE: This document is CONFIDENTIAL. DO NOT CIRCULATE IT TO PERSONS OUTSIDE THE COMPANY.It is a means for
HPE to communicate unique product service support information to HPE personnel.You may discuss the contents in general terms
with a customer without making reference to the document itself or reading it verbatim.

© Copyright 2016 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without
notice.The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements
accompanying such products and services.Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

You might also like