Problem Note 65928: Some SAS® Viya® services fail to start with a "VAULT_CERTIFICATE_ISSUED_ERROR" message
During a new deployment or after applying hot fixes (released after April 1, 2020), some SAS Viya services might not start properly when your machines are using a nonpublic suffix, such as .local or .intra, in the DNS name.
This issue affects but is not limited to the following services:
sas-viya-reportservicesgroup-default
sas-viya-sasvisualanalytics-default
sas-viya-scoreexecution-default
sas-viya-workflow-default
sas-viya-workflowsupport-default
Here are the key words to look for in the logs:
VAULT_CERTIFICATE_ISSUED_ERROR
Below this error, you see messages that are similar to the following:
"o.s.v.a.LifecycleAwareSessionManager : service Cannot enhance VaultToken to a LoginToken: Token self-lookup failed; nested exception is org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://<VAULT_HOST_NAME>:8200/v1/auth/token/lookup-self": Certificate for <VAULT_HOST_NAME> doesn't match any of the subject alternative names ..."
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
SAS System | SAS Viya | Microsoft® Windows® for x64 | 3.5 | 3.5 | Viya | Viya |
Linux for x64 | 3.5 | 3.5 | Viya | Viya |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Some services, such as sas-viya-sasvisualanalytics-default and sas-viya-reportservicesgroup, might fail to start with a "VAULT_CERTIFICATE_ISSUED_ERROR" message.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2020-06-05 07:47:48 |
Date Created: | 2020-05-05 07:22:05 |