Nutanix Troubleshooting

NOTE: The troubleshooting items below are only applicable when Nutanix support is enabled, and are to be used along with VMware Troubleshooting.

Cluster Connection

If the connection to your Nutanix Cluster or Nutanix Controller Virtual Machines is lost, the following log messages and exceptions may appear in the error.log:

"Failed to start connection; nested exception is:"

"net.schmizz.sshj.transport.TransportException: Broken transport; encountered EOF"

"java.net.ConnectException: Connection times out: connect"

Nutanix Cluster not available for any cluster service stop operations

This error may occur if the Cluster is down when PowerChute attempts to stop the Cluster. This could also happen if your Nutanix Cluster credentials have changed after configuring PowerChute. Ensure the correct Cluster/Controller VM credentials are provided via the PowerChute Setup wizard, or the Nutanix Settings screen.

The error below is written to the PowerChute Event Log:

"Could not connect to the Nutanix Cluster. Cannot stop Nutanix Cluster services."

Nutanix Cluster cannot be stopped

This can be caused by an unsuccessful attempt to stop AFS or an unsuccessful attempt to power off all User VMs. To resolve this issue, ensure you configure a sufficient duration to successfully stop AFS and power off all the User VMs.

The error below is written to the PowerChute Event Log:

"Cluster cannot be gracefully shut down."

Unable to start Nutanix Cluster

Cluster may not start if the time drift is incorrectly set. To check if the time between the individual Controller VMs is correctly synchronized, execute the following command:

allssh date

For information on configuring time synchronization for your Nutanix Cluster, see the following recommendations from Nutanix.

This could also happen if your Nutanix Cluster credentials have changed after configuring PowerChute. Ensure the correct Cluster/Controller VM credentials are provided via the PowerChute Setup wizard, or the Nutanix Settings screen.

The error below is written to the PowerChute Event Log:

"Cluster cannot be started."

Acropolis File Services (AFS)

Unable to stop AFS

If AFS cannot be successfully stopped, the Cluster cannot be stopped and Controller VMs cannot be gracefully shut down. To resolve this issue, increase the AFS stop duration. It is recommended that you manually test the time needed to stop AFS on your Cluster and specify that as the duration in the PowerChute UI.

To do this, connect to any Controller VM while AFS is running, and use the following command:

afs infra.stop <fileservername>

Note the duration it takes for the AFS service to fully stop and use this as the AFS Shutdown Duration in the Virtualization Settings screen in the PowerChute UI.

The error below is written to the PowerChute Event Log:

"Nutanix AFS cannot be gracefully shut down."

The error below is written to the PowerChute error.log:

"Failed to stop Nutanix AFS: [error received]"

Protection Domain

Unable to abort Protection Domain Replications

For information on why this did not abort, refer to the error message generated in the error.log.

The error below is written to the PowerChute Event Log:

"Nutanix Protection Domain replications cannot be gracefully aborted."

The errors below is written to the PowerChute error.log:

"Failed to retrieve Protection Domains replication status: [error received]"

"Failed to abort ongoing Protection Domain replications: [error received]"

Unable to disable Metro Availability

Metro Availability may not be disabled if Metro Availability was not correctly set up on the Cluster.

For more information, refer to the error message generated in the error.log.

The error below is written to the PowerChute Event Log:

"Nutanix Metro Availability cannot be disabled."

The error below is written to the PowerChute error.log:

"Failed to disable Protection Domains Metro Availability: [error received]"

Unable to re-enable Metro Availability

Metro Availability may not be re-enabled if Metro Availability was not correctly set up on the Cluster.

For more information, refer to the error message generated in the error.log.

The error below is written to the PowerChute Event Log:

"Nutanix Metro Availability cannot be enabled."

The error below is written to the PowerChute error.log:

"Failed to enable Protection Domains Metro Availability: [error received]"