You might receive the following message after performing a search:

Possible Causes

This is a generic message that indicates that an error occurred in the Elasticsearch cluster. There can be many causes for this message, including an Elastic node becoming unavailable, an out-of-memory exception, and so on.

If you encounter this error, review the svi-sand service and Elasticsearch log files for the time period when the message was displayed to better understand what the root cause might be.
 

Rare Cause on SAS^® Visual Investigator 10.6 and SAS^® Visual Investigator 10.7: Search Guard Signing Key

This section covers one possible explanation for this error that is very rare and occurs only on SAS Visual Investigator 10.6 – 10.7 (and associated hot fixes). SAS^® Visual Investigator 10.8 is not affected by this issue.

If searches fail for all users, it is possible that the SIGNING_KEY has not been set for Search Guard.
 

Determine Whether the Search Guard Signing Key Is the Cause

Complete these steps to confirm whether this issue is the cause:

1. Open the sg_config.yml file in the /opt/sas/viya/home/libexec/elasticsearch-secure/plugins/search-guard-6/sgconfig/ directory.  
2. Compare the SIGNING_KEY parameter to the JWT verifier key for SASLogon, which is located in the /opt/sas/viya/config/etc/SASSecurityCertificateFramework/private/jwt-privatekey.pem directory.

If the SIGNING_KEY parameter and the JWT verifier key for SASLogonare are the same, then this issue is not the cause for the error.
 

Resolution If the Search Guard Signing Key Is the Cause

If you confirm that the parameter and key are different, then complete these steps to resolve the issue:

1. Open the sg_config.yml file in the /opt/sas/viya/home/libexec/elasticsearch-secure/plugins/search-guard-6/sgconfig/ directory.  
2. Set the SIGNING_KEY parameter to the JWT verifier key for SASLogon, which is located in the /opt/sas/viya/config/etc/SASSecurityCertificateFramework/private/jwt-privatekey.pem directory.
3. Force Search Guard to pick up the new verification key by running the following commands on the primary:

4.  Run the following command on each Elastic Search Master node where saslogonhost and saslogonport are the host name and port of the primary:

5. Restart the svi-sand service.

Operating System and Release Information