Connection to SASApp issue

[sathya66]

We have an issue with SAS Server 9.4 been installed on Linux machines and users are trying to connect from Windows EG8.1 and DI 9.4.

It was working fine until yesterday and no more issue. From today, when users Connected in EG or DI and tried to expand/access Serves >SASApp- its hung. Keep processing, nothing happens and cannot see the libraries and Files.

I have verified the ObjectSpawner is running and no ERRORS in the object  logs. Validated and connected  workspace and pooled WS server successfully from SMC Client and SMC from Servers.

[sas@testmeta Logs]$ grep -i test_user ObjectSpawner_2022-04-26_testcompute_26252.log

2022-04-26T09:27:56,866 INFO  [00138874] :test_user - New client connection (11702) accepted from server port 8591 for user test_user. Encryption level is Credentials using encryption algorithm SASProprietary. Peer IP address and port are [::ffff:11.97.200.95]:55168 for APPNAME=SAS Enterprise Guide.

2022-04-26T09:27:56,894 INFO  [00138874] :test_user - Created process 66342 using credentials test_user (child id 193).

2022-04-26T09:41:32,787 INFO  [00139273] :test_user - New client connection (11761) accepted from server port 8591 for user test_user. Encryption level is Credentials using encryption algorithm SASProprietary. Peer IP address and port are [::ffff:11.97.200.95]:64199 for APPNAME=SAS Enterprise Guide.

2022-04-26T09:41:32,814 INFO  [00139273] :test_user - Created process 69745 using credentials test_user (child id 196).

[sas@testmeta Logs]$ grep -i error ObjectSpawner_2022-04-26_testcompute_26252.log

What would be issue not able to find and fix for this? Any suggestion?

[jcFranklin]

I would suggest enabling workspace server logging as a next step: https://documentation.sas.com/doc/en/bicdc/9.4/bisag/p0atyzdgfzbsjfn1j4bbbt14ic7t.htm

Then you can trace the connection using the object spawner log and the workspace server log to see where it is getting hung up at. You want to look at the time stamps. I can see from what you sent that the process is getting created quickly, but we need to know how long it took the client to enter the workspace server session, how long the workspace server took to initialize, and where in the process the hanging is occurring.

You can reference my SGF paper to help with tracing the connection and to look at the possible causes: https://www.sas.com/content/dam/SAS/support/en/sas-global-forum-proceedings/2018/2003-2018.pdf

[sathya66 · Accepted solution]

Found the issue and resolved. It is to do with our DBMS server issue/outage. We have preassigned DBMS libraires so SAS EG is taking time to connect to SASApp. I have tested this with nopreassigment option in the SAS workspace server from SMC and restarted Objectspawner.