I'm not aware of any plans to support external Redis. ... View more

If the liveness probe fails enough, Kubernetes will restart the pod, so you may need to use kubectl logs --previous to see the logs that include the failure. ... View more

No, using external Redis is not an option. ... View more

A 401 unauthorized response usually suggests an issue with the token you're using (whereas 403 forbidden means you have a permissions issue). You may need to get a fresh token. For the _webout issue you might want to check _omitSessionResults is set to false. Control When the Compute Provider Saves Results https://go.documentation.sas.com/doc/en/sasadmincdc/v_064/caljobs/p1xrrmzo4afphbn1pn3j9hqfd5rv.htm#n1sda1twhq33ytn1sqslo2oc33lu ... View more

What version of SAS Visual Analytics are you using? ... View more

You appear to be successfully authenticating to Viya using an authorization code, so your REST API request to run the job is successful. This triggers a request from job-execution to compute to run the code. To do so, compute attempts to start a compute server through a request to the launcher service, which would submit the attempt to the launcher server. The "Access Denied" error is coming from the launcher server when authenticating against the host. If you store a valid user ID and password to launch the process on the compute server host for your identity under Environment Manager > My Credentials in the DefaultAuth domain, is the launch successful? ... View more

I believe both the OpenSearch Dashboards UI and python script have a limit of 10,000 records you can export at a time. ... View more

The getlogs.py in viya4-monitoring-kubernetes/logging/bin is the easiest way (in my opinion) to pull the relevant lines out. ./getlogs.py -fo csv -l ERROR -c <container-name> -m 10000 -o errors.csv -st 2025-08-04 00:00:00 (7 days ago) You can also export the results using opensearch dashboards. For alerting you would need to use Grafana, which I think would require configuring OpenSearch as a data source for Grafana. Display Log Messages in Grafana Dashboards https://go.documentation.sas.com/doc/en/obsrvcdc/v_003/obsrvdply/p1bqqaa7r8s06jn1pjexe3ymrckn.htm You could then build alerts based using the datasource. Manage Grafana Alerting https://go.documentation.sas.com/doc/en/obsrvcdc/v_003/obsrvug/n1eslak1oy1dq4n1d9nbtuqefwpb.htm ... View more

If the Metadata Server is already running, it would explain why a new one cannot start, as the port would already be in use. ... View more

When the Metadata Server fails to start, it should still create a log file in <SASConfig>\Levn\SASMeta\MetadataServer\Logs (default path). That log would contain any errors causing the startup failure. If no log is created, you may need to check the Windows Event Viewer for the failure. ... View more

No, that isn't correct. Applying patch updates, version upgrades, or changes to your configuration by rebuilding a reapplying your assets would not remove your existing configurations. Those are persisted in the sas-viya-consul-data-volume-* PVCs. ... View more

The example PatchTransformer $deploy/sas-bases/examples/sas-compute-server/config/compute-server-add-nfs-mount.yaml shows how to add a volume to podTemplates with the label sas.com/template-intent=sas-launcher, which would include batch and compute servers. Since you'd be adding a PVC instead of an NFS volume, instead of: nfs: path: {{ PATH-TO-BE-MOUNTED }} server: {{ HOST }} you would use: persistentVolumeClaim: claimName: {{ PVC-NAME }} Your LDAP and oauth configurations are persisted in the SAS Configuration Server, so these would not be lost when pods are restarted or you apply new assets. ... View more

When SAS Studio starts it assigns a temp fileref "_keepalv". It then calls /compute/sessions/<session-id>/filerefs/_keepalv periodically to maintain activity on the session and prevent the compute server from terminating due to inactivity. The compute server log may have some detail on why this fileref is inaccessible. ... View more

Each user would need to store their host launch credentials (user ID and password) under the DefaultAuth authentication domain. Whenever their host credential password changed as @AhmedAl_Attar mentioned they would need to update this. Your users could store a credential using the Enterprise Guide, SAS Management Console, or Personal Login Manager desktop applications, or through the SAS Environment Manager mid tier application (https://midtier.example.com:8343/SASEnvironmentMgrMidTier/). Environment Manager - Update a Stored Password https://go.documentation.sas.com/doc/en/bicdc/9.4/evadmfun/n1rx8gbcz1v4jcn1rhnnbxgdh495.htm#n01imi2ex150rfn102y94vzgs92f SAS Management Console - Update the Password in a Login https://go.documentation.sas.com/doc/en/bicdc/9.4/mcsecug/n1kxhdu1ams2rzn180hnad7xwzm1.htm#n028hk1vq5owo0n1msv1j69x27ot ... View more