Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Resolved issues

Reference number

Area affected

Description

ENS-4344

Database service

The Database service cannot be run on additional instances if any instance of that service is down

In these situations, you cannot configure the Database service to run on additional instances:

The Database service has a status of Failed on one of the instances in the system.

One of the instances is down and the Database service is configured to run on that instance.

Fix: In the situations listed above, you can now successfully run the Database service on additional instances without first having to remove failed system instances or Database service instances from the system.

ENS-4523

Updates

Update fails with RMIServer stub error

Rarely, an instance may fail to be restarted during a system update and the Administration App may display this error message:

java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException

In this situation, retrying the update does not cause the update to run successfully.

Workaround

To successfully complete the update:

1.Use SSH to log into the instance that failed to restart.

2.Navigate to the installation directory.

3.Run the stop script:

<hci-install-directory>/bin/stop

4.Restart your system on the instance. For example:

oIf you ran your system in the foreground, run:

sudo <hci-install-directory>/bin/run

oIf you ran your system using systemd, run:

sudo systemctl start <product-name>.service

5.On the Updates page in the Administration App, click on the Retry button to restart the update.

Fix: This issue may still rarely occur when updating to release 1.2.1 but no longer occurs when updating from 1.2.1 to a later release.

ENS-4613

run and stop scripts
The stop script fails when run with a different path from the run script

The stop script fails to run if you run it with a different path than the run script.

For example, you can run the run with a path relative to the system installation directory:

sudo ./bin/run

If you then attempt to run the stop script with a full path, the script fails:

sudo /opt/hci/bin/stop

realpath: ./bin/run: No such file or directory

Fix: The stop script no longer fails in this situation.

Trademarks, Legal disclaimer, Third-party software in this documentation

© 2017 Hitachi Vantara Corporation. All rights reserved.

 

  • Was this article helpful?