Vertica support has requested something called Scrutinize output for analysis while investigating an issue reported against the Data Repository Database servers. How is this data gathered to honor the request?
How to generate Vertica scrutinize logging diagnostics package for support analysis.
Data Repository, all versions
To generate the requested Scrutinize diagnostic data in order to help us investigate the issue involved, complete the following steps.
Run the utility as the dradmin user.
Execute the following command:
/opt/vertica/bin/scrutinize -U '<username>' -P '<password>' -m '<CaseNumber>'
Please note that the username, password and CaseNumber values must be in single quotes for the scrutinize process to gather all of the data necessary to debug many issues.
The scrutinize process will still run and collect system data if this isn't done, but it will be missing this vital information if the command is not formatted correctly.
For example if the DB user name is dradmin, the password (the same one used to stop/start the Vertica DB from the adminTools UI) is dbpass (default from the guides), the command run might look like this:
/opt/vertica/bin/scrutinize -U 'dradmin' -P 'dbpass' -m '00123456'
You can also include the -z switch, to include a certain number of old vertica.logs. The following example includes 5 previous Vertica logs.
/opt/vertica/bin/scrutinize -z5 -U 'dradmin' -P 'dbpass' -m 'Case 00123456'
When the process is completed, please upload the resulting VerticaScrutinize.<date>.zip file to the support case for analysis.