Running scrutinize
Important
This section details the implementation ofscrutinize
that executes commands with Admininstration Tools (admintools). For details about scrutinize
with vclusterops
, the Go library that executes commands with a REST interface, see scrutinize for VerticaDB.
You can run scrutinize
with the following command:
$ /opt/vertica/bin/scrutinize
Unqualified, scrutinize
collects a wide range of information from all cluster nodes. It stores the results in a .tar
file (VerticaScrutinize.
NumericID
.tar
), with minimal effect on database performance. scrutinize
output can help diagnose most issues and yet reduces upload size by omitting fine-grained profiling data.
Note
scrutinize
is designed to collect information for troubleshooting your database and cluster. Depending on your system configuration, logs generated from running scrutinize
might contain proprietary information. If you are concerned with sharing proprietary information, please remove it from the .tar
file before you send it to Vertica Customer Support for assistance.
Command options
scrutinize
options support the following tasks:
-
Obtain version information about
scrutinize
and Vertica, and online help. -
Upload results to Vertica Customer Support.
Privileges
In order for scrutinize
to collect data from all system tables, you must have superuser or SYSMONITOR privileges; otherwise, scrutinize
collects data only from the system tables that you have privileges to access. If you run scrutinize
as root when the dbadmin user exists, Vertica returns an error.
Disk space requirements
scrutinize
requires temporary disk space where it can collect data before posting the final compressed (.tar
) output. How much space depends on variables such as the size of the Vertica log and extracted system tables, as well as user-specified options that limit the scope of information collected. Before scrutinize
runs, it verifies that the temporary directory contains at least 1 GB of space; however, the actual amount needed can be much higher.
You can redirect scrutinize
output to another directory. For details, see Redirecting scrutinize output.
Database specification
If multiple databases are defined on the cluster and more than one is active, or none is active, you must run scrutinize
with one of the following options:
$ /opt/vertica/bin/scrutinize {--database=database | -d database}
If you omit this option when these conditions are true, scrutinize
returns with an error.