We got a weird issue in our SAS environment. All of the sudden users were not able to connect the SAS Servers. SAS services such as ObjectSpawner and Metadata Server were running fine. It is obvious that there is no issue with metadata as the user was login to the application. To make this issue more complex we didn’t find any error in the log file.
When the user try to connect to the server (by clicking on the + button in SAS Enterprise Guide) all they can see is Windows hour glass. It is not throwing any error except for few where the dialog box showed a error pointing to IOM. However we can’t make any sense of them.
Following are the investigation we made during the issue:
1. Modification in configuration file by checking the date
2. Permission change to workspaceserver.sh
3. File system mounted properly
4. Whether files are creating in SASWORk while connecting to SAS EG
5. Firewall problems by pinging from local to host (server)
6. Checked command history
7. Irresponsive Objectspawner
8. Whether able to launch SAS from SAS Foundation
9. Invoking Workspace Server from batch
10. Whether SAS jobs running using batch server
11. I/O issues
12. SASWORk and SASHOME configuration
13. Abnormal configuration made in sasv9.cfg and autoexec file
I know it is a huge list as the issue lasted for four days. We almost found the issue when we are not able to invoke Workspace server from batch.
To invoke Workspace from batch use following command:
./workspaceserver.sh –nodms
It should return something like 1? where we can write SAS code. If it is not returning 1? Then try using following command.
./workspaceserver.sh –nodms –metaautoresources dummy
If the above command returns you the 1?, then it is probably the problem with pre-assigned library.
To confirm it, create a new workspace server and don’t assign any library to it. You will be able to connect to the newly created server.
When the user try to connect to the server (by clicking on the + button in SAS Enterprise Guide) all they can see is Windows hour glass. It is not throwing any error except for few where the dialog box showed a error pointing to IOM. However we can’t make any sense of them.
Following are the investigation we made during the issue:
1. Modification in configuration file by checking the date
2. Permission change to workspaceserver.sh
3. File system mounted properly
4. Whether files are creating in SASWORk while connecting to SAS EG
5. Firewall problems by pinging from local to host (server)
6. Checked command history
7. Irresponsive Objectspawner
8. Whether able to launch SAS from SAS Foundation
9. Invoking Workspace Server from batch
10. Whether SAS jobs running using batch server
11. I/O issues
12. SASWORk and SASHOME configuration
13. Abnormal configuration made in sasv9.cfg and autoexec file
I know it is a huge list as the issue lasted for four days. We almost found the issue when we are not able to invoke Workspace server from batch.
To invoke Workspace from batch use following command:
./workspaceserver.sh –nodms
It should return something like 1? where we can write SAS code. If it is not returning 1? Then try using following command.
./workspaceserver.sh –nodms –metaautoresources dummy
If the above command returns you the 1?, then it is probably the problem with pre-assigned library.
To confirm it, create a new workspace server and don’t assign any library to it. You will be able to connect to the newly created server.
Comments
Post a Comment