The elasticsearch service, a component of the Notifications cache, is only accessible from the local machine.
Verify this service is running and serving requests.
Procedure:
$ smarts/bin/sm_service show.
The expected result is:
RUNNING smarts-elasticsearch
Windows browser example:
http://localhost:9200/_status
A page specific to the browser will appear.
Linux examples:
curl -XGET http://localhost:9200/_status
curl http://localhost:9200/smarts/alert/_count
A JSON page appears indicating success and shows Smarts as one of the indices:
For example:
"_shards":{"total":10,"successful":5,"failed":0}
...
"indices":{"smarts":...
Note: After elasticsearch is started, it may take a few minutes before the setup script begins running.
In some instances, elasticsearch appears to be running, but not resolving to localhost, causing configuration checks to not be satisfied.
When running the following:
curl -XGET http://127.0.0.1:9200
confirmation is needed that the localhost is resolving to the server, but elasticsearch was not:
<HTML>
<HEAD><TITLE>Redirection</TITLE></HEAD>
<BODY><H1>Redirect</H1></BODY>
[root@SERVER-FQDN bin]#
Then run the following:
service elasticsearch status
=====================================================
Redirecting to /bin/systemctl status elasticsearch.service
Unit elasticsearch.service could not be found.
======================================================
If the above message is received, reboot the server.