Can’t login to the Reporting UI


Can’t log in to the Reporting UI, and getting a “The server is not responding, please contact your administrator.” error. The reporting.log is throwing the following error:

  • ERROR [20XX-XX-XX XX:XX:XX,XXX] Attempt to use search service for 0 threw a dreadful exception.
  • ! org.elasticsearch.discovery.MasterNotDiscoveredException: null
  • ! at$AsyncSingleAction$4.onTimeout(
  • ! at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(
  • ! at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(
  • ! at org.elasticsearch.cluster.service.ClusterService$
  • ! at org.elasticsearch.common.util.concurrent.ThreadContext$
  • ! at java.util.concurrent.ThreadPoolExecutor.runWorker(
  • ! at java.util.concurrent.ThreadPoolExecutor$
  • ! at


The error is caused by Reporting being unable to query Elasticsearch for a master node, which also indicates there is an issue with the Elasticsearch cluster.

Resolution Steps

Validate Elasticsearch node(s)

Validate each Elasticsearch node is up and running. Please follow the steps below:

  1. SSH to the SEARCH NODE(s) as the Interset User.
  2. Type in the following command to see if Elasticsearch responds without errors:
    • curl -ks -X GET http<s>://<SEARCH_NODE_FQDN>:9200/_cluster/health?pretty
  3. Type in the following command to validate the status of Elasticsearch:
    • sudo systemctl status elasticsearch
  4. If Elasticsearch is not running, please type in the following command to start Elasticsearch:
    • sudo systemctl start elasticsearch
  5. Type in the following command to view the interset.log in the Elasticsearch log (/var/log/elasticsearch) directory:
    • sudo less /var/log/elasticsearch/interset.log
  6. In the interset.log hit the follow key combination jump to the end of the log:
    • Shift + G
  7. When a node starts up properly, the following will be outputted in the interset.log file:
    • [20XX-XX-XXT09:39:49,674][INFO ][o.e.h.HttpServer ] [<REPORTING_NODE_FQDN>] publish_address {<REPORTING_NODE_FQDN>:9200}, bound_addresses {<REPORTING_NODE_FQDN>:9200}
    • [20XX-XX-XXT09:39:49,674][INFO ][o.e.n.Node ] [<REPORTING_NODE_FQDN>] started
      • NOTE: The Elasticsearch node that is chosen as the master for the Elasticsearch cluster will have the following outputted in the interset.log:
        • [20XX-XX-XXT09:39:49,080][INFO ][o.e.c.s.ClusterService ] [<REPORTING_NODE_FQDN>] master {new {<REPORTING_NODE_FQDN>}{XzM9TSt3Ql62Pp6Y9WHW1A}{uEFlJWWNQDu8b5F-B84eiA}{<REPORTING_NODE_FQDN>}{<REPORTING_NODE_IP>:9300}}, removed {{<REPORTING_NODE_FQDN>}{bS8-wLAzTma9gAeDFRAQwg}{6szmJfWCSAyQqp8nS-SYbw}{<REPORTING_NODE_FQDN>}{<REPORTING_NODE_IP>:9300},}, added {{<REPORTING_NODE_FQDN>}{bS8-wLAzTma9gAeDFRAQwg}{yA2X3jZJTECJrrJMC6PSDA}{<REPORTING_NODE_FQDN>}{<REPORTING_NODE_IP>:9300},}, reason: zen-disco-elected-as-master ([2] nodes joined)[{<REPORTING_NODE_FQDN>}{bS8-wLAzTma9gAeDFRAQwg}{yA2X3jZJTECJrrJMC6PSDA}{<REPORTING_NODE_FQDN>}{<REPORTING_NODE_IP>:9300}, {<REPORTING_NODE_FQDN>}{RYYfDVzETQCcx-cBAsDInw}{77ZlAVlNTfuHYjBgLXToLw}{<REPORTING_NODE_FQDN>}{<REPORTING_NODE_IP>:9300}]
        • [20XX-XX-XXT09:40:18,357][INFO ][o.e.c.r.a.AllocationService] [<REPORTING_NODE_FQDN>] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[entity_stats_0_20XX-XX-XX_00:51:13][3]] ...]).
  8. After all Elasticsearch nodes are up and running, type in the following command to verify if the cluster is up and running:
    • curl -ks -X GET http<s>://<REPORTING_NODE_FQDN>:9200/_cluster/health?pretty
  9. The output will be similar to the following:
    • {
    •   "cluster_name" : "interset",
    •   "status" : "green",
    •   "timed_out" : false,
    •   "number_of_nodes" : 4,
    •   "number_of_data_nodes" : 3,
    •   "active_primary_shards" : 152,
    •   "active_shards" : 304,
    •   "relocating_shards" : 0,
    •   "initializing_shards" : 0,
    •   "unassigned_shards" : 0,
    •   "delayed_unassigned_shards" : 0,
    •   "number_of_pending_tasks" : 0,
    •   "number_of_in_flight_fetch" : 0,
    •   "task_max_waiting_in_queue_millis" : 0,
    •   "active_shards_percent_as_number" : 100.0
    • }

Validate Reporting UI

  1. Open up a web browser and navigate to the Reporting UI URL:
  2. Log in to the Reporting UI as the Reporting admin. The default credentials for the Reporting admin user are as follow:
    • Username: admin
    • Password: password
  3. If the login is successful, the issue has been resolved.
  4. If the login failed, please look at the reporting.log which is located in the /opt/interset/log directory on the REPORTING NODE, and investigate if there are any further errors.

If further is assistance is required, please contact Interset Support (

Applies To

  • Interset 5.4.x or higher
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request