CAS worker nodes fail to start and the CAS Controller log contains errors if you perform steps similar to the following:

1. You deploy SAS^® Viya^® with Ansible.
2. You customize the casenv_user variable in the vars.yml file.
3. You update the sas-tkcas file via a manual yum or rpm command instead of running the Viya Ansible playbook to perform the package update.

After you perform these steps, permissions on CAS config files are reverted to the default file and directory ownership settings, causing errors similar to the following to appear in the log:

INFO [00000004] castest5 local MAIN NoUser [casutil.c:452] - An error message was found launching a process on another machine, [Configuration Options Failure. Exiting]
INFO [00000004] castest5 local MAIN NoUser [casutil.c:452] - An error message was found launching a process on another machine, [2018-05-09T21:30:28 cas3.example.com:2: ERROR: cannot open /opt/sas/viya/config/etc/cas/default/node.lua: Insufficient authorization to access /opt/sas/viya/config/etc/cas/default/node.lua.]
INFO [00000004] castest5 local MAIN NoUser [casutil.c:452] - An error message was found launching a process on another machine, [Configuration Options Failure. Exiting]
INFO [00000004] castest5 local MAIN NoUser [casutil.c:452] - An error message was found launching a process on another machine, [2018-05-09T21:30:28 cas2.example.com:1: ERROR: cannot open /opt/sas/viya/config/etc/cas/default/node.lua: Insufficient authorization to access /opt/sas/viya/config/etc/cas/default/node.lua.]
INFO [00000004] castest5 local MAIN NoUser [casutil.c:452] - An error message was found launching a process on another machine, [Configuration Options Failure. Exiting]

To circumvent the problem, complete these steps:

1. Run the following command on any CAS secondary controllers (if applicable) and each CAS worker node:
   

sudo /opt/sas/viya/home/bin/cas_setup.sh -r /opt/sas -d viya -i default

In a multi-tenant environment, repeat this command for each tenant, using the tenant ID in the -d option. Here is an example:

sudo /opt/sas/viya/home/bin/cas_setup.sh -r /opt/sas -d tenant-ID-1 -i default
sudo /opt/sas/viya/home/bin/cas_setup.sh -r /opt/sas -d tenant-ID-2 -i default

2. Restart the CAS server by running the following command on the CAS controller node:

sudo service sas-viya-cascontroller-default restart

In a multi-tenant environment, repeat this command for each tenant. Here is an example:

sudo service sas-tenant-ID-1-cascontroller-default restart
sudo service sas-tenant-ID-2-cascontroller-default restart