SAS VIYA Single Node install fails CAS Service fails

[Pate]

Single Node  Viya Cluster

All ids are local .sasinstall id is used for deployment.It has sudo access

sas sas

cas sas( passwordless ssh)

sasinstall sas (passwordless ssh and sudo)

postgres postgres

apache apache

sasrabbitmq sas

saspgpool sas

Error is UseHostToken specified in non-root launcher

[alexal]

@Pate ,

I would like to review output from these commands:

ls -ld /opt/sas/viya/home/SASFoundation/utilities/bin/caslaunch
cat /etc/fstab

[Pate]

-rwsr-xr-x. 1 root root 116037 Jul 9 2018 /opt/sas/viya/home/SASFoundation/utilities/bin/caslaunch

/etc/fstab
/dev/mapper/rhel_ppviyap-root / xfs defaults 0 0
UUID=c0bd9a2e-7872-4b39-90e6-9ff4ba577f28 /boot xfs defaults 0 0
/dev/mapper/rhel_ppviyap-home /home xfs defaults 0 0
/dev/mapper/rhel_ppviyap-swap swap swap defaults 0 0
/dev/sdb1 /opt/sas auto nosuid,nodev,nofail 0 0
/dev/sdb2 /sasdata auto nosuid,nodev,nofail 0 0
/dev/sdb3 /saswork auto nosuid,nodev,nofail 0 0
/dev/sdb4 /sascache auto nosuid,nodev,nofail 0 0

[yatinrao]

Anyone found a solution to this? , I am having the same error

[alexal]

@yatinrao ,

See my response above about nosuid.

[alexal]

@Pate ,

You have to remove nosuid option from /opt/sas mount:

/dev/sdb1 /opt/sas auto nosuid,nodev,nofail 0 0

[yatinrao]

Alex

see myfstab below , /opt/sas is mounted without nosuid option . 

I have also tried to comment UseHostToken in the /opt/sas/viya/home/SASFoundation/utilities/bin/launchconfig file

without any success 

/dev/mapper/rhel-root / xfs defaults 0 0
UUID=ede57cdd-e3cc-49d4-b04a-e28dcba47338 /boot xfs defaults 0 0
UUID=F799-E84E /boot/efi vfat umask=0077,shortname=winnt 0 0
/dev/mapper/rhel-home /home xfs defaults 0 0
/dev/mapper/rhel-var /var xfs defaults 0 0
/dev/mapper/rhel-var_log /var/log xfs defaults 0 0
/dev/mapper/rhel-var_log_audit /var/log/audit xfs defaults 0 0
/dev/mapper/rhel-swap swap swap defaults 0 0
/dev/mapper/Volgrp01-lv--yum--cache /var/cache/yum xfs defaults 0 0

/dev/mapper/Volgrp01-lv--sas /opt/sas xfs defaults 0 0

/dev/mapper/Volgrp01-lv--cache1 /cache1 xfs defaults 0 0
/dev/mapper/Volgrp01-lv--tmp /tmp xfs defaults 0 0
# /dev/mapper/Volgrp01-lv--sas--viya--logging /opt/sas/viya xfs defaults 0 0
/dev/mapper/Volgrp01-lv--sas--tmp /sastmp xfs defaults 0 0

[alexal]

@yatinrao ,

I have also tried to comment UseHostToken in the /opt/sas/viya/home/SASFoundation/utilities/bin/launchconfig file

Do not do that.

Show me output from a command shown below

ls -ld /opt/sas/viya/home/SASFoundation/utilities/bin/caslaunch

Also, I would like to see CAS server logs from /opt/sas/viya/config/var/log/cas/default directory.

[yatinrao]

Alex 

I un-commented the useHostToken and externalIdent

here is the output from ls -ld 

[root@wnysas03 bin]# ls -ld /opt/sas/viya/home/SASFoundation/utilities/bin/caslaunch
-rwxr-xr-x+ 1 cas sas 116037 Jul 9 2018 /opt/sas/viya/home/SASFoundation/utilities/bin/caslaunch

I had also tried the following , ansible reverts it back to cas:sas 

chown root:root /opt/sas/viya/home/SASFoundation/utilities/bin/caslaunch

chmod u+s /opt/sas/viya/home/SASFoundation/utilities/bin/caslaunch

I have attached the logs from /opt/sas/viya/config/var/log/cas/default.

Thanks 

Yatin

[alexal]

@yatinrao ,

I had also tried the following , ansible reverts it back to cas:sas

Ansible? When? Are you sure? That file should be owned by root with sticky bit set, otherwise, you won't be able to start the CAS server.

[yatinrao]

Alex 

I am in the config stage of the ansible playbook ,  ansible stops in this step "TASK [casserver-config : started CAS Service]" 

since I am running ansible in debug, I can apply changes in a separate ssh session.  when ansible resumes it reverts ownership to cas:sas 

Should the sticky bit be set for /opt/sas/viya/home/SASFoundation/utilities/bin directory ? 

here is what it looks like 

[root@wnysas03 utilities]# pwd
/opt/sas/viya/home/SASFoundation/utilities
[root@wnysas03 utilities]# ls -al
total 12
drwxr-xr-x+ 5 cas sas 39 Jun 19 16:09 .
drwxr-xr-x+ 7 cas sas 99 Jun 28 12:37 ..
drwxr-xr-x+ 3 cas sas 8192 Jul 25 08:36 bin
drwxr-xr-x+ 3 cas sas 18 Jul 17 10:52 man
drwxr-xr-x+ 3 cas sas 18 Jul 17 10:53 src

[alexal]

@yatinrao ,

Should the sticky bit be set for /opt/sas/viya/home/SASFoundation/utilities/bin directory ? 

No.

Someone else is reverting these permissions. Do you have something like Chef or Puppet? 

[yatinrao]

No , I checked for both chef and puppet 

its got to be ansible changing ownership

Yatin

[yatinrao]

Issue resolved .  

The error was a result of incorrect playbook generated by incorrect SAS orchestration cli.

We had regenerate the playbook.

Thanks Alexal for your help 

[alexal]

I’m glad that the problem has been resolved.