beautypg.com

HP Matrix Operating Environment Software User Manual

Page 112

background image

1.

Modify the configuration file (shown in the default location) at C:\Program Files\HP\
Virtual Server Environment\conf\hp_lsa_service.conf

.

2.

Add the following line. (Change additional.2 to additional.3 if a line with
additional.2

already exists; change additional.2 to additional.4 if lines with

additional.2

and additional.3 already exist, and so on.)

wrapper.java.additional.2=-XX:PermSize=32m -XX:MaxPermSize=128m

3.

Restart the HP Logical Server Automation service.

Error saving storage pool entry after Logical Server Automation service is
restarted

After restarting the HP Logical Server Automation service, you may see the following error when
you try to save a storage pool entry on the Add/Modify Storage Pool Entry screen:

Software caused connection abort: socket write error

Suggested action

Do not shut down or restart the HP Logical Server Automation service while operations are being
performed on logical servers. In this specific case:

1.

Sign out of Insight Dynamics and close the browser window.

2.

Open a new browser window and sign into Insight Dynamics.

3.

Retry the operation.

Restart Logical Server Automation service after VMware vCenter failure

After a VMware vCenter failure, information about ESX Hosts and virtual machines in the logical
server database is not updated, and a refresh of logical server resources may run for longer than
30 minutes or time out in the browser.

Suggested action

After vCenter is restarted, use the Report

→Logical Server Job Status... menu selection to make sure

that there are no logical server operations in progress. Then, restart the Logical Server Automation
service.

Profile is created but not associated with a logical server when service is
stopped during logical server activation

If the first activation of a new logical server is in progress when the HP Logical Server Automation
service is stopped, the logical server definition may be left in a state where the Virtual Connect
profile has been created but is not associated with the logical server. When the logical server is
in this state, an attempt to activate it will fail with the following error:

Unable to create profile {profile name}. (Cannot perform server profile operation because:
Server profile name {profile name} is duplicate. Another server profile with the same name
already exists in VCEM. Verify all the server profile information is correct
and perform the operation again.)

112

Troubleshooting