sas file on mac on linux having problems

Sas-viya-httpproxy-default (this starts and dynamically reloads crucial configuration for HTTPD on RHEL or apache2 on SUSE)Īfter all of these services are started and healthy, the remaining SAS Viya services can be started. Sas-viya-sasdatasvrc-* (multiple services for SAS ® Infrastructure Data Server/PostgreSQL)

There are two key services that must be healthy before other SAS Viya services are started. The services and the order in which they need to be started are as follows:ġ. sas-viya-consul-default: This service is deployed on all machines in the SAS Viya deployment. Machines assigned to the consul host group in inventory.ini during SAS Viya deployment run Consul in server mode, while other machines run as Consul clients.Ģ. sas-viya-vault-default: This service is deployed on all machines assigned to the Consul host group in inventory.ini during SAS Viya deployment, so it is co-located with machines that act as Consul servers.Īfter those two services are started and healthy on all nodes on which they are deployed, the following services should be started. The start-up order for these services is not important, but they must be started after Consul and Vault and before the rest of the SAS Viya services.

In a multi-machine environment, always start the core services that are outlined here before running /etc/init.d/sas-viya-all-services. This SAS Note describes techniques for troubleshooting and resolving SAS Viya 3.5 service start-up problems on Linux. This information expands upon information from General Servers and Services: Operate (Linux) in the SAS ® Viya ® 3.5 Administration Guide. As noted in that documentation, the sas-viya-all-services script does not span multiple machines.

Sas file on mac on linux having problems