Monitoring database start, stop, create, drop database

@DieterC : That information can be found in vertica.log as in when the database was stopped, started etc... the path is dbname/v_dbname_nodexxx_catalog/vertica.log.

In addition, the following info can be useful in case one kills the Vertica process without evidence in the vertica.log or
Drop the database, or recreate it with the same name, logrotate or replace vertica.log

1. Spread starts are written to file: /Your_catalog_path/Your_db_name/dbLog
2. Each time Vertica starts or stopped, the following file will change with a new process ID: /Your_catalog_path/DB_name/v_DbName_NodeName/vertica.pid
   One can monitor the file like so:
   nohup tail -F /Your_catalog_path/DB_name/v_DbName_NodeName/vertica.pid > /tmp/check_pid.log 2>&1 &
   tail -F keep trying to open the file if it is inaccessible while Vertica is down.
3. Each time one will drop the database, this directory will be removed: /Your_catalog_path/DB_name
   One can monitor if this directory is deleted with something like: inotifywait -m /Your_catalog_path/DB_name >> /tmp/DB_stat.log

Thank you Moshe and Sruthi,

• I do assume vertica.log processing needs to be done for all nodes in the cluster as these are not synchronized?
• could admintools.conf or admintools.log be a source of info? Are these synchronized over the nodes?
• If I had a wish I would want metadata at the cluster level (a level higher than the database)
  Something like the v_catalog schema on a cluster level. Is there a thing close to this?

Thank you
Dieter