Know the location and content of system log files and monitor them on a regular basis and not just when problems arise.
The following table shows the locations of the various Greenplum Database log files. In file paths:
$GPADMIN_HOMErefers to the home directory of the
gpadminoperating system user.
$MASTER_DATA_DIRECTORYrefers to the master data directory on the Greenplum Database master host.
$GPDATA_DIRrefers to a data directory on the Greenplum Database segment host.
hostidentifies the Greenplum Database segment host name.
segprefixidentifies the segment prefix.
Nidentifies the segment instance number.
dateis a date in the format
||Many different types of log files, directory on each server.
||system initialization log|
||segment host start log|
||segment host stop log|
||segment instance start log|
||master and segment database logs|
||mirror segment database logs|
||primary segment database logs|
||Global Linux system messages|
gplogfilter -t (
--trouble) first to search the master log for messages beginning with
PANIC:. Messages beginning with
WARNING may also provide useful information.
To search log files on the segment hosts, use the Greenplum
gplogfilter utility with
gpssh to connect to segment hosts from the master host. You can identify corresponding log entries in segment logs by the
Greenplum Database can be configured to rotate database logs based on the size and/or age of the current log file. The
log_rotation_size configuration parameter sets the size of an individual log file that triggers rotation. When the current log file size is equal to or greater than this size, the file is closed and a new log file is created. The
log_rotation_age configuration parameter specifies the age of the current log file that triggers rotation. When the specified time has elapsed since the current log file was created, a new log file is created. The default
log_rotation_age, 1d, creates a new log file 24 hours after the current log file was created.
Parent topic: System Monitoring and Maintenance