11-16-2017 02:15 AM - edited 11-16-2017 05:05 AM
I am unable to connect to a workspace server.
I was created a month ago and i was able to connect to it till yesterday.
There have been no configuration changes in system.
When i try to validate the server the screen just hangs an i could only see a small dailog box saying Validating and after that nothing happens.
Please suggest what steps should i take to check this issue.
Thanks in advance !!
11-16-2017 03:47 AM
11-16-2017 04:38 AM
11-16-2017 05:08 AM
See if those logs are current. If the latest log file has not been written to recently, it's a sign for a hanging process.
Try to connect to the spawner from SMC and restart it from there. If that doesn't work, you may have to use the commandline to kill and restart the spawner process. Which may reveal a configuration problem that keeps the spawner from starting up.
All the while take care that you are following down the right path (looking on the correct physical server, looking for the correct userid - upcase/lowcase! - and so on), and use the correct userid from the commandline. The spawner runs under the userid of the SAS install user.
11-16-2017 04:55 AM
when it stoped working for you, have you changed your password, recently? Is it your account locked, somehow?
If that is the case, your admin should grant you access to change the password on lsf (lspasswd command line).
Anyway, if it is a workspace you can always debug on several ways:
- If you can, connecting to the OS and launching a WorkspaceServer.sh/.bat session and checking what is there.
- Enabling WorkspaceServer logs, temporarily, and extending info to INFO or even DEBUG
- You can also extend log info on Object Spawner, it will require you to refresh or restart the Object Spawner
- Your system admin can check the PAM logs
- You can check logs on LSF.
I would start just with the question regarding the password than perhaps the 2-3 first questions, it should be enough.
11-16-2017 05:03 AM
11-16-2017 10:20 AM
It seems to me that this node has lost a configuration, or perhaps you just need to restart the Object Spawner on that machine. You will need to, anyway, because of the change on logging config.
01-18-2018 05:51 PM
I know this topic is a couple of months old, but we have been experiencing the same issue since December 6, intermittently, and we are getting around by restarting the ObjectSpawner in our compute machines, 4 in a grid environment. Is there a known root cause for this behavior to occur? We contacted SAS tech support and we were told that we need to install 2 hot fixes (N22016 and N27004) we are running SAS 9.4 M1. We are scheduled to apply the hot fixes this weekend, and we hope this will correct the issue with the spawner.
01-19-2018 03:10 AM
Please let us know how it works after the hotfixes application. Every case might be different. I have seen different kind of scenarios that this might happen, on GIR and no GRID environments.
Is your environment windows or linux based? How many connections are in the pool for your SAS Stored Process servers on each SASApp?
On my experience, there is a small bug in SAS 9.4M1 (and further if I am correct) and it should be more stable on later versions. But I have also seen that if you increment the number of connections on the pool for the STP servers it helps to make Object Spawners more stable. The reason is that long or too often STP sessions can make the STP server to crash, eventually, and this can cause, in some scenarios, a domino effect that makes crush the Object Spawner itself. Hence, extending the pool and some other settings in the STP servers (with no hotfixes) can reduce, in some scenarios, availability from 75% to 99%.
01-19-2018 09:28 AM
Thank you very much for your reply, I am a fairly new SAS Admin and I am learning as I go :-). We are running on Linux RHEL 6.7. I will post the results after our hot fix patch.
Need further help from the community? Please ask a new question.