This is documentation for EA software. It may contain information that is out of date and subject to change. Last updated: 3 October 2018.

Gateway Hub Troubleshooting User Guide

Overview

This guide to help you troubleshoot problems in your Gateway Hub instance.

Procedures

How to generate a diagnostics file

There is a script included in every node that creates a diagnostics file that can be sent to support to help diagnose problems.

This diagnostics file includes all the logs, system information, Kafka topics, hbase table information and more.

To create a diagnostics file, run the following command with sudo privileges:

/opt/hub/bin/hub-diagnostics.sh

This creates a .tar.gz file in /tmp/hub-diagnostics. This file can be fetched from the server using scp.

How to verify that your node services are running

The MapR admin interface provides you a lot of information regarding the status and health of your nodes.

Log into the MapR admin instance by entering https://<hostname>:8443 in a web browser, replacing <hostname> with the hostname of the Gateway Hub server:

  • Use the username and password of your Gateway Hub runtime user.
  • Click Log In.

In the Overview tab, there are several sections that provide you with information regarding your MapR instance.

If your instance is healthy:

  • All nodes in the Node Health section are blue.
  • There are no alerts in your Active Alarms section.

Note: It is expected in Cluster Utilization for the memory usage to be high.

How to check your licence status

  1. Log into the MapR admin instance by entering https://<hostname>:8443 in a web browser, replacing <hostname> with the hostname of the Gateway Hub server:

    • Use the username and password of your Gateway Hub runtime user.
    • Click Log In.

  2. Navigate to Admin > Cluster Settings using the toolbar at the top of the page.
  3. On the Admin / Cluster Settings page, select the Licenses tab.

The status of your licences is displayed in a table.

How to verify the REST endpoint is reachable

Use a browser, a dedicated client such as Postman, or curl -k in the command line, to query the REST address followed by /v0/admin/info. The default REST address is https://<hostname>:8080.

If the REST endpoint is reachable, this returns output similar to below:

{
  "buildDateTime" : "2018-07-31T15:50:31.02Z",
  "version" : "1.0.0-EA",
  "gitCommit" : "b27b5dadde830029cdb50c1ea834a34a0663ff62",
  "gitBranch" : "release/1.0.0",
  "javaInfo" : {
    "vendor" : "Oracle Corporation",
    "version" : {
      "major" : 1,
      "minor" : 8,
      "patch" : 0,
      "update" : 181,
      "arch" : "x64"
    },
    "vm" : "OpenJDK 64-Bit Server VM"
  },
  "os" : {
    "name" : "Linux(3.10.0-693.el7.x86_64)",
    "other" : [ "NAME=\"Red Hat Enterprise Linux Server\"", "VERSION=\"7.4 (Maipo)\"", "ID=\"rhel\"", "ID_LIKE=\"fedora\"", "VARIANT=\"Server\"", "VARIANT_ID=\"server\"", "VERSION_ID=\"7.4\"", "PRETTY_NAME=\"Red Hat Enterprise Linux Server 7.4 (Maipo)\"", "ANSI_COLOR=\"0;31\"", "CPE_NAME=\"cpe:/o:redhat:enterprise_linux:7.4:GA:server\"", "HOME_URL=\"https://www.redhat.com/\"", "BUG_REPORT_URL=\"https://bugzilla.redhat.com/\"", "REDHAT_BUGZILLA_PRODUCT=\"Red Hat Enterprise Linux 7\"", "REDHAT_BUGZILLA_PRODUCT_VERSION=7.4", "REDHAT_SUPPORT_PRODUCT=\"Red Hat Enterprise Linux\"", "REDHAT_SUPPORT_PRODUCT_VERSION=\"7.4\"", "Red Hat Enterprise Linux Server release 7.4 (Maipo)", "Linux version 3.10.0-693.el7.x86_64 (mockbuild@x86-038.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Thu Jul 6 19:56:57 EDT 2017" ]
  }
}