Return
-
Title
Vasd debug level details -
Description
This article is to provide details of each debug-level for vasd. -
Resolution
In general vasd is not meant to normally be ran with debug enabled unless troubleshooting. If something horrible happens, it should be sent to syslog regardless of debug. Otherwise it will just report on minor things, like processes starting / stopping. But if something is being tracked down by troubleshooting, then we will need level 5, because we won't know where the issue is ( level wise ), and what message might help in figuring out the issue.
Here is some information from the header file about the debug levels :
VAS_LOG_DEBUG_NONE, /* no debugging */VAS_LOG_DEBUG_1 , /* critical debug messages */VAS_LOG_DEBUG_2 , /* standard application debug messages*/VAS_LOG_DEBUG_3 , /* verbose application and libvas debug messages */VAS_LOG_DEBUG_4 , /* libldap/kerberos debug messages */VAS_LOG_DEBUG_5 , /* libldapcommon debug messages */VAS_LOG_DEBUG_6 /* libvasdb debug messages */If you just want to watch vasd without too much information, you can set it to level 2 or 3.
Here is the information on the vas.conf setting debug-level = <0|1|2|3|4|5|6>
Default value: 0This option controls whether vasd will log debug messages to syslog at the LOG_DAEMON facility and the LOG_DEBUG level. syslog must be configured to capture that type of message correctly in order to capture the vasd debug output. vasd does not log debug messages by default. Setting this option to a value between 1 and 6 will produce debug output from vasd with higher values producing more debug output. Note that you must restart vasd after modifying this option in order for it to take effect. You should only use debug levels of 3 or higher temporarily when troubleshooting due to the large amounts of debug information produced which can quickly fill up syslog. When temporarily debugging vasd, you can use the -d and -g command line options to print debugging information to stderr while running vasd from the command line. Refer to Quest KB article SOL27000 (http://support.quest.com) for detailed steps to enable vasd debug logging. The following example shows how to configure vasd to use a debug level of 2.[vasd]debug-level = 2
For information on how to enable vasd debug to capture more information please click the blue KB number: KB27000