Return
-
Title
Running states of vasd -
Description
What are the different states of vasd, and how do I check? -
Cause
Knowing which state that vasd is in can assist with troubleshooting. -
Resolution
The vasd process essentially has 4 states:
1. Not running.
2. Running, but not handling requests.
3. Running, but only using its cache for handling requests in a disconnected state. For more information about a disconnected state, please refer to https://support.oneidentity.com/kb/4265166/when-does-vasd-go-into-disconnected-mode.
4. Running, and handling requests by querying Active Directory.
How do I check to see which state vasd is currently in?
By executing the following command you will get a numeric output which is "0" to "6". In the example below, the output is "6":
[root@sas512 ~]# ps -ef | grep "[.]vasd" | wc -l
6
What do these numbers mean?
0 - vasd is not running.
1 to 5 - vasd is running, but it is not handling requests or querying Active Directory. It may be using its cache which might be out of date. It depends upon how long it has been in this state for.
6 - vasd is running, and it is handling requests by querying Active Directory.
It is also important to know whether or not the parent is running with the dispatcher. By running the following command, you will know: /opt/quest/libexec/vas/sugi/asdcom SendPing && echo Dispatcher responding
The output should look like this:
[root@sas511 ~]# /opt/quest/libexec/vas/sugi/asdcom SendPing && echo Dispatcher responding
Dispatcher responding
It is also important to know whether or not vasd is operating in a disconnected state, which can be determined by the following command: /opt/quest/libexec/vas/sugi/asdcom GetConnectedStatus
If the output is "SAS daemon is operating in a disconnected state", then vasd is unable to query Active Directory, and is using its cache which was obtained from the last time that it was able to query Active Directory. If the output is "SAS daemon is operating in a connected state", then vasd is properly querying Active Directory.