[HX] Internal service call failed. Please check configuration

[jisoo.han]

We using HXDP 3.0 version, and when I check the status of the HX cluster, it shows that the status is normal. However, in the HX cluster service check section, it fails with the message 'Internal service call failed. Please check configuration.' It seems like there are no issues with the configuration, but what else should I check?

p.s we don't have customer support service

[KyoCode]

Hi,

with a GUI issue as "Internal Service call failed" is regarding tomcat or API services, which are NOT necessarily the same as Hypercheck Cluster services check, the first one requires restarting just management services and maybe some missing files.

In the other hand, Hypercheck will fail when there are services not running, but it also happens that those services might not be enabled by default, such as HyperV SMB client (in ESXi environment is useless), replication, disk encryption, and so on and so forth.

So there are a few torubleshootings regarding "Internal Service call failed" that TAC can perform to restore web GUI (at least a valid SNTC contract can help) even with unsupported HX versions.

Regarding Hypercheck report, there's an extra directory create alongside current .txt file which contain the log information about all checks performed and the outputs, so you can compare and diagnose properly. 

Note: Hypercheck version 4.2 will check more than expected for a HX cluster 3.0, so maybe a few things needs to be checked out manually to be safely ignored,

hope that helps,

AIV

[Steven Tardy]

<Shot in the dark>
That old HX 3.0 version should have `hxdpservices` available. Rather than knowing which individual services to restart, all management (not data plane) services could be restarted in one-fell-swoop.

On each SCVM (one at a time) try:

/bin/hxdpservices stop
/bin/hxdpservices start

Reference (yes this doc is a newer version and yes this doc is Hyper-V, but `hxdpservices` is a mostly undocumented command):
https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/HyperFlex_Upgrade_Guide_for_Hyper_V/4-5/b-hx-upgrade-guide-for-microsoft-hyper-v-4-5/m_troubleshooting.html

[lkamal]

HI , I have issue after physically migrated the hyperflex cluster , as when trying to login to the controller VM to Start the HX cluster , and input the command (HXCLI about ) , it display {Internal server error (500) , Could not connect to internal service . please check the configuration }.,also the datastores showed unmounted  from the HX connect