Using Service Verification

The service verification feature provides an easy way to verify that services on all nodes in the cluster are running and functional.

IMPORTANT Service verification is not currently implemented for all services. Support for additional services will be added in subsequent releases.
For secure or non-secure clusters, you can run the service verification feature from the Installer user interface. Service verification is useful after a new installation. For example, service verification can detect whether all services have successfully joined a cluster. You can run a service verification any time after the cluster is installed to check the general health of services on all nodes.

Before Using Service Verification

Before you can use the service verification feature:
  • The cluster must be installed, and you must have installed it by using the Installer or Installer Stanzas.
  • Ensure that the Installer is up to date. Service verification is supported only on Installer versions and later.
  • Service verification can only be performed from the Installer node. The Installer node is the node where you run the Installer.
  • Running service verification requires root-user access (or sudoer access to root) for remote authentication. (When you perform service verification, the Installer node must ssh into each of the cluster nodes.)

Performing Service Verification Using the Installer User Interface

To perform service verification from the Installer user interface:
  1. On the Installer node, use a browser to navigate to the Installer home page, and log on as the cluster admin:
    https://<Installer Node hostname/IPaddress>:9443
  2. Scroll down until you see the following links:

  3. Click the Show service verification info link to display the list of services and nodes.
  4. Click Run Service Verification to start the verification. The Installer prompts for the root user password:Configure Remote Authentication
  5. Enter the root user credentials, and click Run Service Verification. Verification can take anywhere from a few seconds to several minutes, depending on the size of the cluster, the network, and other attributes that affect performance. When the verification activity is complete, the Installer shows a list of services with the verification output for each service. For example: Service Verification Output
    Possible values are:
  6. To rerun service verification – for example, after running it once and discovering some services are not responding – click Run Service Verification again.

Service Verification Logs

On each node where a service is installed, logged output from the service verification feature is saved to:
For example, service verification output for OpenTSDB might be found here:
# pwd
# ls
metrics_tmp                    ot_purgeData.log-20210414.gz
opentsdb_daemon.log            ot_purgeData.log-20210415.gz
opentsdb.err                   ot_purgeData.log-20210416.gz
opentsdb_install.log           ot_purgeData.log-20210417.gz
opentsdb.out                   ot_purgeData.log-20210418.gz
opentsdb_scandaemon.log        ot_purgeData.log-20210419.gz
opentsdb_scandaemon_query.log  ot_purgeData.log-20210420.gz
opentsdb_startup.log           ot_purgeData.log-20210421.gz
opentsdb_startup.log.1         ot_purgeData.log-20210422.gz
opentsdb_startup.log.2         ot_purgeData.log-20210423.gz
opentsdb_startup.log.3         ot_purgeData.log-20210424.gz
opentsdb_startup.log.4         ot_purgeData.log-20210425.gz
ot_purgeData.log               ot_purgeData.log-20210426.gz
ot_purgeData.log-20210404.gz   ot_purgeData.log-20210427.gz
ot_purgeData.log-20210405.gz   ot_purgeData.log-20210428.gz
ot_purgeData.log-20210406.gz   ot_purgeData.log-20210429.gz
ot_purgeData.log-20210407.gz   ot_purgeData.log-20210430.gz
ot_purgeData.log-20210408.gz   ot_purgeData.log-20210501.gz
ot_purgeData.log-20210409.gz   ot_purgeData.log-20210502.gz
ot_purgeData.log-20210410.gz   ot_purgeData.log-20210503
ot_purgeData.log-20210411.gz   queries.log
ot_purgeData.log-20210412.gz   verify_service.20210503_101756
The following is an example of the log output for the Open TSDB service:
# more verify_service.20210503_101756
Starting verifier at Mon May  3 10:17:59 PDT 2021
checking to see if pid 664447 is alive
pid 664447 is alive
checking to see if opentsdb pid 664447 is responsive
opentsdb responded - rc=0, output = [{"metric":"cpu.percent","tags":{"clustername":"","clusterid":"6923574301854689047"},"a
Possible return codes for the log output are:
  • 0 – running and responding to a simple interaction test
  • 1 – not running
  • 2 – running but not responding to a simple interaction test
  • 3 – not started*
*From Warden's point of view, the service is enabled, but Warden has not started it yet.

Performing Service Verification Using the mapr-installer-cli

To perform service verification for all nodes from the command line:
  1. On the Installer node, navigate to the installer directory:
    cd /opt/mapr/installer
  2. Run the following command:
    ./bin/mapr-installer-cli verify_services -n -o config.ssh_id=root -o config.ssh_password=<password>
    For example:
    ./bin/mapr-installer-cli verify_services -n -o config.ssh_id=root -o config.ssh_password=<password>
    MapR Installer SDK
    Logging in to localhost
    Verifying Services...
    100% [ ==================================================================================================== ]