Unable to Explore Digital Hive Content

Unable to Explore Digital Hive Content

Question

When using the Explore Content interface to browse the Digital Hive content, a message stating "Something went wrong" and a Try Again button is displayed How do I resolve this?



Answer

This issue is usually a result of Elasticsearch being unreachable. The first thing to verify is that both Elasticsearch services are active. If either of the services is offline, restart the Elasticsearch 5.5.1 (DigitalHive_9200) and Elasticsearch 5.5.1 (DigitalHive_9201) services.

If Digital Hive is configured for load balancing, where Digital Hive and Elasticsearch are installed on multiple servers, there may be a configuration issue with Elasticsearch. To help diagnose this issue, examine the <Digital Hive install>/app/node1/tomcat/logs/theia.date.log file for the presence of this error message:

ERROR [c.m.a.r.SearchController] - Error while getting ES indices 
org.elasticsearch.client.ResponseException: GET http://server_name4:9201_all/_settings,_aliases?human: HTTP/1.1 503 Service Unavailable
{"error":{"root_cause":[{"type":"master_not_discovered_exception","reason":null}],"type":"master_not_discovered_exception","reason":null},"status":503}

Examine the <Digital Hive install>/Elasticsearch/logs/theia_es_1/theia-cluster.log (and theia_es_2) directory for the presence of this error message:

[server_name_9200] failed to send join request to master ... [127.0.0.1:9400] handshake failed. unexpected remote node ...

The key element to this message is that instead of the actual server IP address, the 127.0.0.1 (localhost) IP is being used. 

To correct this misconfiguration, files on both the primary and secondary servers will have to be verified.

Primary Elasticsearch configuration changes

Edit the <Digital Hive install>/Elasticsearch/config1/elasticsearch.yml file so that these settings are consistent
  1. network.bind_host: "0.0.0.0"
  2. network.publish_host: "primary server name or IP address"
  3. discovery.zen.ping.unicast.hosts: primary server name or IP address:9400
  4. Save and close the file
Edit the <Digital Hive install>/Elasticsearch/config2/elasticsearch.yml file so that these settings are consistent
  1. network.bind_host: "0.0.0.0"
  2. network.publish_host: "primary server name or IP address"
  3. discovery.zen.ping.unicast.hosts: primary server name or IP address:9400
  4. Save and close the file
Restart the Elasticsearch 5.5.1 (DigitalHive_9201) service
Restart the Elasticsearch 5.5.1 (DigitalHive_9200) service, if it didn't start automatically after the previous step


Secondary Elasticsearch configuration changes

Edit the <Digital Hive install>/Elasticsearch/config1/elasticsearch.yml file so that these settings are consistent
  1. network.bind_host: "0.0.0.0"
  2. network.publish_host: "secondary server name or IP address"
  3. discovery.zen.ping.unicast.hosts: ["primary server name or IP address:9400","primary server name or IP address:9401"] 
  4. Save the changes to the file
Edit the <Digital Hive install>/Elasticsearch/config2/elasticsearch.yml file so that these settings are consistent
  1. network.bind_host: "0.0.0.0"
  2. network.publish_host: "secondary server name or IP address"
  3. discovery.zen.ping.unicast.hosts: ["primary server name or IP address:9400","primary server name or IP address:9401"] 
  4. Save the changes to the file
Restart the Elasticsearch 5.5.1 (DigitalHive_9201) service
Restart the Elasticsearch 5.5.1 (DigitalHive_9200) service, if it didn't start automatically after the previous step

Open a new browser tab, or log out the current Digital Hive session, and log into Digital Hive. The issue should now be resolved and content should be visible through the Explore Content interface.

For more information regarding load balancing for Digital Hive, please consult this knowledge base document: https://support.digitalhive.com/portal/en/kb/articles/digital-hive-failover


    • Related Articles

    • Discoverable Search Feature Overview

      Overview By default, the only content that appears for a user in Digital Hive is the content that the user would see if they logged into the BI system(s) as themselves. In other words, Digital Hive will not expose content to a user that they are not ...

    • Search Management Interface

      Getting to the Search Management Interface 1. Click the user avatar and select Manage Digital Hive 2. Within the Control Center expand Content then click Search 3. Here you will find the new search and indexing features to better manage indices ...

    • How to 'Enable' Connector Content Within Digital Hive

      Question Once the connector parameters for a content system have been successfully applied, how do I select the desired content from the source to appear within Digital Hive? Answer As part of the connector creation process, once the required ...

    • Users are 'Unable to log in right now' to Digital Hive

      Question Some users who were able to log into Digital Hive previously are now unable to access the Digital Hive application. When they try to log in with their credentials, they receive an error message stating 'Unable to log in right now'. How do we ...

    • Content has Disappeared from the Digital Hive Interface

      Question It appears that all of the content has disappeared from the Digital Hive interface. When an Administrator accesses the Explore Content tool from their avatar, a blank screen is returned. How do we restore the view of the content? Answer This ...