State of a CAS Controller to be shown as grey (not running?) instead of green for only a single user

[tonycord]

Hello there.

What can cause the state of a CAS Controller to be shown as grey (not running?) instead of green (running) in the Servers page, in SAS Environment Manager (screenshot below), for only a single user (as far as I know)?

 

The single affected user cannot access CAS data sources. I've checked with five more users and none of them reported this problem.

Environment info:

• SAS Viya 3.5 environment
• MPP mode
• Linux deployed
• Kerberos authentication.

[gwootton]

This suggests the user can get a list of CAS servers, but is unable to start a CAS session. Does the user encounter an error when attempting to get a CAS session in SAS Studio? Are there corresponding errors in the CAS log?

[Sajid01]

Is this impacted user able to work in SASStudioV. ?

[tonycord]

The user can launch SAS StudioV and run scripts, except the ones requiring a CAS server Session.

[tonycord]

Yes, the user does encounter an error when attempting to get a CAS session in SAS Studio: 

ERROR: Connection failed. Server returned: Failed to launch session controller.: Failed to launch session worker.ERROR: Unable to connect to Cloud Analytic Services xxxxxxx.xxxxxx.xxxxxx on port 5570. Verify connection parameters and        retry.

Do you mean the log from a specific source? If so, which one (cas, consul, rabbit ...)?

[gwootton]

This confirms the user is not able to get a CAS session as the cause of the server state showing as grey.

The logs for CAS (/opt/sas/viya/config/var/log/cas/default) might shed some light on why the session failed to launch. If you are using CASHostAccountRequired for the user and that user is not able to own a process on one of the workers this could explain it.

[michele_sas · Accepted solution]

Hi @tonycord

You said you are using Kerberos authentication.  There is some helpful information in section "Validate Kerberos Configuration" in SAS Help Center: Authentication: How To   that can also be helpful when looking at the CAS log. 

[tonycord]

thanks @michele_sas . I'll look into it.

by the way, I noticed that the home folder for this one particular user was missing in one of the three available cas workers, which is odd because there's no manual process involved. 

[tonycord]

Hello again, @michele_sas .

Indeed there was a problem with the kerberos configuration of one of the CAS Workers.I failed to mention that this specific user is a new user, sorry about that. I guess that explains the reason why only this specific user had no home folder in the Worker and could not create a CAS Session.  

Thank you for your help.