How to enable vasd debug to capture more information (27000)

Below are the steps for enabling vasd debug to capture more information about what is happening.

1. Enable vasd debugging by running:
# /opt/quest/bin/vastool configure vas vasd debug-level 5

NOTE: If troubleshooting Starling 2FA issues run this command as well.

# /opt/quest/bin/vastool configure vas starling debug-level 5

2. Configure the System Logger configuration file for the operating system to capture debug.

The name of the file, location, and setting may vary. Refer to the operating system vendor for more information. The most common configuration is below:

Edit the syslog.conf or rsyslog.conf (or appropriate syslog config) file and add *.debug line and specify a file for the output like below:

*.debug               -/tmp/vas_debug.log

When configuring syslog please note the following:

• Some operating system require the key to be used instead of spaces after "*.debug"
• If rsyslog is being used, make sure that the following change is also made to turn off rate limiting so that no log messages are lost. After the line that includes "$ModLoad imuxsock" add these two lines:

$SystemLogRateLimitInterval 0
$SystemLogRateLimitBurst 0

• If the file /etc/systemd/journald.conf exists on your system that may also have rate limiting that can be disabled with these lines:

• By default syslog will sync logs to disk after every new entry. This can cause excessive disk usage when vasd debug is enabled. We recommend adding a - (minus) to the beginning of the log file name in syslog which means that writes are not synced immediately. This will reduce disk usage with the risk that some log messages are lost if your system crashes.

3.Create the log file:

# touch /tmp/vas_debug.log

4. Restart the syslog daemon:
# systemctl restart syslog

5. Restart the journald daemon:

# systemctl restart systemd-journald

6. Reproduce the steps that had failed earlier or wait for the issue to occur again.

Please save the date command and the commands done to reproduce the failure in a text document.  

NOTE: VASD does not need to be restarted on 4.0 and later. It will read the changes and start logging debug within 30 seconds. However depending of the level of debug expected and the state of the system or vasd process, a vasd restart is recommended.

6.  Once the issue has been reproduced or occurred, review the debug file to ensure that it contains data.

7.  Attach a copy of the text file with the commands and data and the debug file to the Service Request.

8. To remove the debug do the following:

1. Unconfigure vasd debugging:
# /opt/quest/bin/vastool configure vas vasd debug-level

NOTE: If you configured for Starling debug then run this command as well.

# /opt/quest/bin/vastool configure vas starling debug-level

2. Remove the *.debug line that you added to syslog.conf and reverse the modification (if any) to the lines after $ModLoad imuxsock

3. Reverse the changes made to /etc/systemd/journald.conf

4. Restart the syslog process

5. restart the journald process

6. After you have reviewed or sent the log file to support it can be safely removed.
# rm /tmp/vas_debug.log