SAS 9.4 M5 installation issue

[Keerthip]

Hi All,

We have done a fresh install of SAS 94 M5. All the sas services are up in Metadata and Grid control node. Object spawners are up in both the servers.

We are unable to validate SASApp Workspace server.

[3/8/18 2:01 PM] INFO: Starting extended validation for Workspace server (level 1) - Making a connection
[3/8/18 2:01 PM] SEVERE: The launch of server SASApp - Workspace Server for user xxxxxx failed.
[3/8/18 2:01 PM] SEVERE: Failed to start the server.
[3/8/18 2:01 PM] SEVERE: The application could not connect to any server in the cluster "(xxxxxxx.net:8591,xxxxxxx1:8591)".

Could some one help me with this issue?

[Kurt_Bremser]

Make sure that the spawners are running on all nodes in the cluster.

[Keerthip]

Yes , Object spawners are up. Still workspace servers are not validating from SAS Management console. But i am able to run sas code lines from linux host using ./sas -nodms.

[Kurt_Bremser]

Next step would be to check the spawner logs if your connection attempts show up. If not, you may have a firewalling issue.

If yes, you might see either you have an access issue, or a problem in starting the SAS process.

[Keerthip]

Below is the object spawner log . Nothing is getting created under workspace server logs.

- Request made to cluster SASApp - Logical Workspace Server (A5EPZ598.AW000006).
2018-03-08T14:05:29,855 INFO [00021337] :xxxx - Redirect client in cluster SASApp - Logical Workspace Server (A5EPZ598.AW000006) to server SASApp - Workspace Server (A5EPZ598.AY00000C) at sesklsasgrndev01.emea.astrazeneca.net:8591.
2018-03-08T14:05:29,929 INFO [00021337] :xxxx - New out call client connection (109) for user sastrust@saspw. Encryption level is Everything using encryption algorithm SASPROPRIETARY. Peer IP address and port are [10.54.180.61]:8561.
2018-03-08T14:05:29,983 INFO [00021337] :xxxx - There are no grid option sets defined for SAS application server "SASApp".
2018-03-08T14:05:29,984 INFO [00000009] :sas - Client connection 109 for user sastrust@saspw closed.
2018-03-08T14:05:30,038 INFO [00021337] :xxxx - New out call client connection (110) for user sastrust@saspw. Encryption level is Everything using encryption algorithm SASPROPRIETARY. Peer IP address and port are [10.54.180.61]:8561.
2018-03-08T14:05:30,078 INFO [00000009] :sas - Client connection 110 for user sastrust@saspw closed.
2018-03-08T14:05:30,249 INFO [00021337] :xxxx- Created grid job 134 using credentials xxxx (child id 12).
2018-03-08T14:05:41,274 ERROR [00021264] :sas - The launch of the server (SASApp - Workspace Server) process failed with an unknown status code (127).
2018-03-08T14:05:41,274 INFO [00021264] :sas - Grid job 134 owned by user xxxx (child id 12) has ended.
2018-03-08T14:05:41,274 ERROR [00021264] :sas - The specified uuid 0BEAF18C-292E-2548-ACAD-A4A86898FB0C did not match any process managed by this spawner.
2018-03-08T14:05:41,274 ERROR [00021337] :xxxx - The launch of server SASApp - Workspace Server for user xxxx failed.
2018-03-08T14:05:41,275 INFO [00021337] :sas - Client connection 108 for user xxxx closed.

[Kurt_Bremser]

This

2018-03-08T14:05:41,274 ERROR [00021264] :sas - The launch of the server (SASApp - Workspace Server) process failed with an unknown status code (127).

is the crucial line IMO.

Log on to the server specified (using a SSH client) with the credentials in question, and check if you can start SAS from the commandline.

Run a simple program in batch, like

proc options;
run;

You might even find that you can't log on because the server suffers from LDAP configuration problems, or can't create the necessary infrastructure (eg SASUSER directory)

Or logging on could fix your problem as the PAM modules active during manual logon create a home directory for a user on their own. Something that the SAS spawner does not yet do, IIRC.

Depending on your findings, you will have to repeat the procedure that fixed the problem on all cluster nodes.

[JuanS_OCS]

Hello @Keerthip,

I agree with @Kurt_Bremser, a good test is to try to launch a workspace server session, locally from the server, I think you will be able to understand more.

Here are my expectations:

• You try to validate Workspace server with sasadm@saspw (I hope not)
• Your user cannot create session in LSF, for that you would need, perhaps, to register your password in LSF with lspaswd (not the first time I see it)
• https://stackoverflow.com/questions/1763156/127-return-code-from
• You are missing some pre-requisites, such as SSH passwordless configuration

[avinashginjupal]

@Keerthip Does your issue got resolved? I don't see this post is marked as solved and we are currently facing same issue our environment. Any help would be appreciated.

[Mark_sas]

Have you followed the suggestions in the previous posts by Kurt and JuanS?