Error validating Workspace server using sasdemo and sassrv user

[Madhan_cog1]

Hi All,

We have installed and configured SAS 9.4 M5(Grid version) in a Linux environment.

We are getting the below error while validating Workspace server with sasdemo and sassrv user.

2020-10-19T08:54:03,814 ERROR [00002792] scesas - The launch of the server (SASApp - Workspace Server) process failed with an unknown status code (255).

2020-10-19T08:54:03,815 ERROR [00002814] scesasdemo - The launch of server SASApp - Workspace Server for user scesasdemo failed.

2020-10-19T08:54:03,815 ERROR [00002792] scesas - The specified uuid 6BE64EBE-7C66-D443-AC99-1A4ED4F925DA did not match any process managed by this spawner.

2020-10-19T08:54:15,244 ERROR [00002904] scesas - The launch of the server (SASApp - Workspace Server) process failed with an unknown status code (255).

2020-10-19T08:54:15,244 ERROR [00002904] scesas - The specified uuid D6DFE387-FE5F-5B43-9050-1E8F7E32CC40 did not match any process managed by this spawner.

2020-10-19T08:54:15,244 ERROR [00002906] scesasdemo - The launch of server SASApp - Workspace Server for user scesasdemo failed.

2020-10-19T08:55:44,025 ERROR [00002991] scesas - The launch of the server (SASApp - Workspace Server) process failed with an unknown status code (255).

2020-10-19T08:55:44,028 ERROR [00003033] scesasdemo - The launch of server SASApp - Workspace Server for user scesasdemo failed.

Could you please suggest what could be the issue.

We are able to connect to Application server using sasdemo user and execute the programs in SAS EG,Stuido etc.

Thanks,

Madhan M.

[AnandVyas]

Hi @Madhan_cog1 

Clear the credentials cache from SMC and try again. Also, "sassrv" should not be used to validate workspace server. You can use "sasdemo".

https://documentation.sas.com/?cdcId=bicdc&cdcVersion=9.4&docsetId=bisag&docsetTarget=p0ekp61ix06nsn...

[Madhan_cog1]

Hi Anand,

We tried clearing the cache but it did not work. We got the same issue .

Thanks,

Madhan M

[AnandVyas]

Hi @Madhan_cog1 

Can you confirm you are using same "sasdemo" ID and password which you are using from EG/Studio? If the connection works from client, it should work from SMC as well.

If it's still the same, I would advise to enable debugging for object spawner logs and capture the results to analyze it further.

https://documentation.sas.com/?cdcId=bicdc&cdcVersion=9.4&docsetId=bisag&docsetTarget=p1cu1oogaxct6j...

[Madhan_cog1]

Hi Anand,

Thanks for the response.

Yes we are using the same "sasdemo" ID and password which we are using from EG/Studio.

As per the link given below we have enabled the debugging for object spawner logs.

Am attaching the log for your reference.

Could you please check and advice.

Thanks,

Madhan M.

[AnandVyas]

Hi @Madhan_cog1 

Thanks for sharing the logs. I can see that the request was submitted and LSF did try to launch a session however it failed. Since you have confirmed that the connection works from EG/Studio I am ruling out below issues:

- User Home directory exist on the all compute nodes.

- LSF process are running as required on all the compute nodes.

Do you have workspace server logs enabled on the compute nodes? Could you please check and advise if the workspace server log was generated or not? If generated, are there any errors reported in that?

Also, Was this setting working before? Did you try restarting object spawner?

[Madhan_cog1]

Hi Anand,

Thanks for the response.

We enabled the Workspace server logs and debugged the issue. It was more of a access issue to the group.

The issue is resolved now.

Thanks,

Madhan M

[AnandVyas]

Hi @Madhan_cog1 

Glad that you were able to get to the root cause after enabling workspace server logs and resolve the issue.

[jcFranklin]

When we see the error " failed with an unknown status code (255)", usually the failure is due to file permission errors. If logging for the WorkspaceServer sessions has been enabled, this is a common source of failure if the users are not able to create the logs due to permissions on the directory holding the logs.

Other sources would be incorrect permissions to create the WORK library, SASWORK being out of space, or, especially in the case of new users, their Unix $HOME directories do not have the correct permissions.

One last cause would be that the permissions on the directories in the <SASConfig> path have been set so that the users are not able to access and execute the WorkspaceServer.sh script.

One way we could try to figure this out, would be to enable more logging, or you can navigate to your Workspace Server directory (sas/config/Lev1/SASApp/WorkspaceServer) and run ./WorkspaceServer.sh -nodms with the failing userid.