Event codes

The following table lists the event codes that Vertica logs to the events system tables.

Event Code	Severity	Event Code Description	Description/Action
0	Warning	Low Disk Space	Warning indicates one of the following issues: Lack of disk space for database Disk failure I/O hardware failure Action: Add more disk space, or replace the failing disk or hardware as soon as possible. Check `dmesg` to see what caused the problem. Also, use the DISK_RESOURCE_REJECTIONS system table to determine the types of disk space requests that are being rejected and the hosts where they are rejected. See Managing disk space for details.
1	Warning	Read Only File System	Database lacks write access to the file system for data or catalog paths. This sometimes occurs if Linux remounts a drive due to a kernel issue. Action: Give the database write access.
2	Emergency	Loss Of K Safety	The database is no longer K-safe because insufficient nodes are functioning within the cluster. Loss of K-safety causes the database to shut down. Action: Recover the system.
3	Critical	Current Fault Tolerance at Critical Level	One or more nodes in the cluster failed. If the database loses one more node, it will no longer be K-safe and shut down. Action: Restore nodes that failed or shut down.
4	Warning	Too Many ROS Containers	Heavy load activity on one or more projections sometimes generates more ROS containers than the Tuple Mover can handle. Vertica allows up to 1024 ROS containers per projection before it rolls back additional load jobs and returns a ROS pushback error message. Action: The Tuple Mover typically catches up with pending mergeout requests and the Optimizer can resume executing queries on affected tables (see Mergeout). If this problem does not resolve quickly, or if it occurs frequently, it is probably related to insufficient RAM allocated to MAXMEMORY in the TM resource pool.
5	Informational	WOS Over Flow	Deprecated
6	Informational	Node State Change	The node state changed. Action: Check node status.
7	Warning	Recovery Failure	Database was not restored to a functional state after a hardware or software related failure. Action: Reasons for the warning can vary, see the event description for details.
8	Warning	Recovery Error	Database encountered an error while attempting to recover. If the number of recovery errors exceeds Max Tries, the Recovery Failure event is triggered. Action: Reasons for the warning can vary, see the event description for details.
9	n/a	Recovery Lock Error	Unused
10	n/a	Recovery Projection Retrieval Error	Unused
11	Warning	Refresh Error	The database encountered an error while attempting to refresh. Action: Reasons for the warning can vary, see the event description for details.
12	n/a	Refresh Lock Error	Unused
13	n/a	Tuple Mover Error	Deprecated
14	Warning	Timer Service Task Error	Error occurred in an internal scheduled task. Action: None, internal use only
15	Warning	Stale Checkpoint	Deprecated
16	Notice	License Size Compliance	Database size exceeds license size allowance. Action: See Monitoring database size for license compliance.
17	Notice	License Term Compliance	Database is not in compliance with your Vertica license. Action: Check compliance status with GET_COMPLIANCE_STATUS.
18	Error	CRC Mismatch	Cyclic Redundancy Check (CRC) returned an error or errors while fetching data. Action: Review the `vertica.log` file or the SNMP trap utility to evaluate CRC errors.
19	Critical/Warning	Catalog Sync Exceeds Durability Threshold	Severity: Critical when exceeding hard limit, Warning when exceeding soft limit.
20	Critical	Cluster Read-only	Eon Mode) Quorum or primary shard coverage loss forced database into read-only mode. Action: Restart down nodes.