This tool collects Greenplum and system log files, along with the relevant configuration parameters, and generates a file which can be provided to VMware Customer Support for diagnosis of errors or system failures.
gpmt gp_log_collector [-failed-segs | -c <ID1,ID2,...>| -hostfile <file> | -h <host1, host2,...>] [ -start <YYYY-MM-DD> ] [ -end <YYYY-MM-DD> ] [ -dir <path> ] [ -segdir <path> ] [ -a ] [-skip-master] [-with-gptext] [-with-gptext-only] [-with-pxf] [-with-pxf-only] [-with-gpupgrade]
gp_configuration_historyto identify when a segment fails over to their mirrors or simply fails without explanation. The relevant content ID logs will be collected.
gp_log_collector, the generated tarball can be very large. Use this option to skip Greenplum Master log collection when only Greenplum Segment logs are required.
gpupgradelogs along with Greenplum logs.
Note: Hostnames provided through
-h must match the hostname column in
The tool also collects the following information:
|Source||Files and outputs|
|Segment server parameters||
|System files from all hosts||
|Database-related files from all hosts||
NOTE: Some commands might not be able to be run if user does not have the correct permissions.
Collect Greenplum master and segment logs listed in a hostfile from today:
gpmt gp_log_collector -hostfile ~/gpconfig/hostfile
Collect logs for any segments marked down from 21-03-2016 until today:
gpmt gp_log_collector -failed-segs -start 2016-03-21
Collect logs from host
sdw2.gpdb.local between 2016-03-21 and 2016-03-23:
gpmt gp_log_collector -failed-segs -start 2016-03-21 -end 2016-03-21
Collect only GPText logs for all segments, without any Greenplum logs:
gpmt gp_log_collector -with-gptext-only