Problem Note 62715: Consul might unexpectedly report that the status of Elasticsearch is "critical" in SAS® Visual Investigator
 |  |  |  |
During or shortly after you update to SAS® Visual Investigator 10.3.1, Elasticsearch might seem to be working fine but Consul reports that the service has a "critical" status.
To work around this issue, deregister and reregister the Elasticsearch health check:
sudo /opt/sas/viya/home/bin/sas-bootstrap-config --token-file /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token agent check deregister --id "elasticsearch"
sudo /opt/sas/viya/home/bin/sas-bootstrap-config --token-file /opt/sas/viya/config/etc/SASSecurityCertificateFramework/tokens/consul/default/client.token agent check register --service-id "elasticsearch" --id "elasticsearch" --name "elasticsearch" --script "/opt/sas/viya/home/share/searchguard/svi-searchguard-healthcheck.sh --healthaddr ip-address-of-ES-client" --interval "10s" --timeout "2s"
Note: In the command, replace ip-address-of-ES-client with the IP address of the machine that hosts the Elasticsearch client.
Then, invoke your restart-vi-apps.sh script. That script should be available in a location similar to the following:
/opt/sas/viya/home/share/svi-configuration/restart-vi-apps.sh
Finally, stop and then restart the Analyze and Index (AI) service.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Visual Investigator | Linux for x64 | 10.3.1 | Viya | ||
Consul might display a status of "critical" for Elasticsearch even though the Elasticsearch health-check value is "green."
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2018-08-08 15:00:16 |
| Date Created: | 2018-08-03 16:22:29 |