Monitoring log files
When a database is running
When a Vertica database is running, each node in the cluster writes messages into a file named
vertica.log. For example, the Tuple Mover and the transaction manager write INFO messages into
vertica.log at specific intervals even when there is no mergeout activity.
You configure the location of the
vertica.log file. By default, the log file is in:
catalog-pathis the path shown in the NODES system table minus the Catalog directory at the end.
database-nameis the name of your database.
node-nameis the name of the node shown in the NODES system table.
NoteVertica often changes the format or content of log files in subsequent releases to benefit both customers and customer support.
To monitor one node in a running database in real time:
Log in to the database administrator account on any node in the cluster.
In a terminal window enter:
$ tail -f catalog-path/database-name/node-name_catalog/vertica.log
NoteTo monitor your overall database (rather than an individual node/host), use the Data Collector, which records system activities and performance. See Data collector utility for more on Data Collector.
||The catalog pathname specified when you created the database. See Creating a database.|
||The database name (case sensitive)|
||The node name, as specified in the database definition. See Viewing a database.|
When the database/node is starting up
During system startup, before the Vertica log has been initialized to write messages, each node in the cluster writes messages into a file named
dbLog. This log is useful to diagnose situations where the database fails to start before it can write messages into
dblog is located at the following path, using
database-name as described above: