Not a problem. Just make sure CAS_DISK_CACHE is available on all of your CAS server nodes (controller and workers). ... View more

Have you had a chance to check the CAS server logs in /opt/sas/viya/config/var/log/cas/default directory? ... View more

Yes, App.tk.eam.ssl will provide more information about the problem in the SAS log. You can also test the connection to the SAS LASR Authorization service using CURL command (run it from the compute tier): curl -v --cacert /<SASHome>/SASSecurityCertificateFramework/1.1/cacerts/trustedcerts.pem https://<MIDDLE_TIER_FQDN>:<PORT>/SASLASRAuthorization ... View more

Duplicate of https://communities.sas.com/t5/SAS-Visual-Analytics/SAS-VA-LASR-ERROR/td-p/685169  ... View more

@yatinrao ,   As I already mentioned in the track. By default, when SAS Viya is deployed, it installs Apache httpd with a self-signed certificate for use across the deployment. It seems like you already have httpd set up, which is using a custom SSL certificate. Are you sure the correct path to the certificates was provided in vars.yml file (option HTTPD_CERT_PATH)?   Please see more details here: https://go.documentation.sas.com/?docsetId=dplyml0phy0lax&docsetVersion=3.5&docsetTarget=n1knvzbsifo9xqn1al0bh7wxrrkg.htm&locale=en#p0k93dyozg2inln15fynq8loz6ox  ... View more

@MariaD ,   Did you check LD_LIBRARY_PATH?   %put LD_LIBRARY_PATH is: %sysget(LD_LIBRARY_PATH) ; ... View more

The mirrormgr utility still has a "verify" command that you can use to verify local repository contents:   Usage: mirrormgr [flags] mirrormgr [command] Available Commands: help Help about any command list List various types of resources mirror Mirror content from SAS repositories verify Verify local repository contents version Show mirrormgr version information ... View more

Please make sure the LASR server has been started with the LOGGING option. Also, let's enable TKMPI_DEBUGONEXCEPTION as described below to see if there are any exceptions. Note below that gstack will also work the same as pstack.  pstack is a symlink to gstack in modern versions of GDB. Check that pstack is installed on all TKGrid nodes, by running 'pstack' at the command line.  If it is, create a file called pstack.sh, which contains:   #! /bin/sh pstack $2 > /tmp/sastb.out  Make the script executable.   Set variables like the following in the /<PATH_TO>/TKGrid/tkmpirsh.sh file on all TKGrid nodes:   export TKMPI_DEBUGGER=/opt/sas/pstack.sh export TKMPI_DEBUGONEXCEPTION=1 After the LASR crash, check /tmp directory on all the machines. One or more may have a traceback in /tmp/sastb.out. Send this file wherever you find it. Also, I would like to review the LASR server logs and /var/log/messages file from all TKGrid nodes. In addition to all, I said above, show me the output from these commands: /<SASHome>/SASFoundation/9.4/utilities/bin/vercon /<SASHome>/SASFoundation/9.4/sasexe/lasr.so ls -ld /<SASHome>/SASFoundation/9.4/sasexe/lasr.so /<SASHome>/SASFoundation/9.4/utilities/bin/vercon /<PATH_TO>/TKGrid/lib/lasr.so /<PATH_TO>/TKGrid/bin/simsh "ls -ld /<PATH_TO>/TKGrid/lib/lasr.so" ... View more

How many LASR servers do you have? All of them are going down? Do they run in a distributed or non-distributed mode? I also would like to know the exact SAS version. ... View more