NOTE: The troubleshooting items below are only applicable when HyperFlex support is enabled, and are to be used along with VMware Troubleshooting.
|
|
NOTE: The troubleshooting items below are only applicable when HyperFlex support is enabled, and are to be used along with VMware Troubleshooting. |
If your HyperFlex credentials are incorrect and PowerChute cannot connect to HyperFlex, the following log messages may appear in the error.log:
"Credentials invalid, returning UNAUTHORIZED"
If your HyperFlex credentials were updated on HyperFlex and not PowerChute, the following log messages may appear in the error.log:
"Credentials invalid, returning UNAUTHORIZED"
Ensure the correct credentials are provided via the PowerChute Setup wizard, or the Communication Settings screen.
If the Controller VMs in your HyperFlex cluster are not available (for example, they are not fully powered on), the following log messages may appear in the error.log:
"Unable to connect to HyperFlex service, returning UNAVAILABLE, error: [error received]"
"Attempt to retrieve token failed, error: [error received]"
Ensure that all Controller VMs in your HyperFlex Cluster are powered on and have the correct IP addresses assigned.
If your HyperFlex Cluster cannot be shut down, ensure that you configure a sufficient duration to successfully stop the cluster service and shut down the cluster. For more information, consult the error.log.
The errors below are written to the PowerChute Event Log:
"Cluster cannot be gracefully shut down."
"The cluster stop operation timed out. Please ensure that sufficient time has been configured."
The errors below are written to the PowerChute error.log:
"Maximum number of retries [retry value] reached, cluster stop failed."
If your HyperFlex Cluster cannot be started, ensure that you configure a sufficient duration to successfully start the cluster service and start up the cluster.
The errors below are written to the PowerChute Event Log:
"Cluster cannot be started."
"The cluster has not started after the cluster start duration has elapsed."
The error below is written to the PowerChute error.log:
"Failed to start HyperFlex cluster."
To successfully shut down Controller VMs, ensure that you configure a sufficient duration to successfully shut down all Controller VMs in the Cluster.
The error below is written to the PowerChute Event Log:
"Controller VM [CVM] did not shut down gracefully."
The errors below are written to the PowerChute error.log:
"Error shutting down CVM: [CVM] - [error received]"
"CVM: [CVM] failed to power off with taskResult: [error received]"
If "Failed to retrieve VM entity for Controller VM" is written to the PoweChute error.log, increase the value of the "VMware_read_timeout" setting in the PowerChute configuration file (pcnsconfig.ini). The default value is 15 seconds, and it is recommended you increase this value to 30 seconds:
[HostConfigSettings]
VMware_connect_timeout = 10
VMware_read_timeout = 30
If the Controller VMs in the Cluster cannot be started, ensure that you configure a sufficient duration to successfully start up all Controller VMs in the Cluster.
The errors below are written to the PowerChute error.log:
"Error starting Controller VM: [CVM] - [error received]"
"Controller VM: [CVM] failed to power on with taskResult: [error received]"