Taking time to connect SASApp through SAS EG.

[ChandanKSAS]

HI,

I am facing an issue, when i'm connecting SASApp Server through SAS EG, it is taking more than 10 minutes to connect. And when validating SAS Workspace server in SMC it is also taking more than 10 minutes to validate. I checked the workspace server log and found IOM ENTRY ServerProxy {compRef:7f83143ef840}->CompDtor() this step taking more than 3 minutes with multiple (4) entry.

Not able to recognize the issue.

Any help will be greatly appreciated.

Thank you!!

[ankitd]

Have you recently performed any configuration changes post which this is occurring or is this a new installation and the issue has begun?

Assuming that host entries have been setup properly or globally defined correctly. If not worth doing that first.

Further, is this limited to just workspace validation or is it related to other IOM Servers i.e. PWS and SP as well?

If this is a Linux deployment, can you try launching SMC via the Linux terminal using X Windows and check the validation.

If this is a windows deployment, try launching  SMC via the windows machine where Metadata/Compute servers have been deployed and validate workspace server.

This will help you understand if there is a proxy issue or something at the network level which could be causing this.

[ChandanKSAS]

@ankitd  this is the old installation in Linux and we didn't do any changes recently, it was working fine just 10 days ago.

This is the test env and it is working normal in prod env.

I also restarted the Objectspawner but still same problem is there.

I validated all the servers under SASApp and problem is only with Workspace server.

Due to some client limitation i can't use X windows here.

[ankitd]

@ChandanKSAS I suppose there has been some accidental changes either in Workspace server configuration via SMC (check this link for IOM bridges -- https://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/iombridge/index.html) you can try to compare it with your production environment for similarity purpose.

The test via X-windows is important to validate to rule out any firewall/network level issues against the port using Workspace server.

While this is just a test and would not be as good as the X-windows, worth checking via the telnet command against the port to ensure there is no lag.

Additionally you can:

Ask tracing to be performed by your OS and Network team while you try to validate the Workspace.

Enable detailed logging on the workspace server and see what is getting captured.

These would help get more clarity.

[ChandanKSAS · Accepted solution]

Resolved, Some pre-assigned library was causing the problem.

[SASKiwi]

If these are libraries connect to external databases then using the DEFER = YES option can improve assignment times.

[SASKiwi]

@ChandanKSAS  - It wouldn't do any harm to simply reboot your whole SAS test environment to see if this clears the problem. It may save you a lot of time troubleshooting.