Because vgptool has out outfile/write-to-file switch, it presents and issue when you need to leave it running. Essentially vgptool offers 2 options: either print to stdout (default) or print to syslog (-l switch). Sending it thru rsyslog can cause you to hit the rate limit. The limit needs to be raised while the debug runs. Also, the template entry in /etc/rsyslog.d/vgp_debug.conf causes the files to be created dynamically, to make things a bit easier to decipher in the end.
------
/etc/rsyslog.d/vgp_debug.conf
$template VGP_DEBUG,"/tmp/yourDir/%timegenerated%.log"
-------
------
/etc/rsyslog.conf
under #### MODULES #### add:
# Disable rate-limiting of log entries
$SystemLogRateLimitInterval 0
$SystemLogRateLimitBurst 0
under #### RULES #### add:
:programname,contains,"vgptool" ?VGP_DEBUG & ~
-------------
-------------
/etc/opt/quest/vgp/vgp.conf
[daemon]
DebugLogLevel = 6
Or
vgptool config daemon DebugLogLevel 6
-----------------
Test rsyslog.conf configuration using 'rsyslogd -N 1 -f /etc/rsyslog.conf'...errors will be clearly stated Restart rsyslog Restart vasd (habit for me after all these years)