|Pivotal Greenplum (GPDB)||4.3.x|
gpcrondump is a wrapper to the gp_dump script that backs up the Greenplum database. Before starting the actual backup (which is called gpdump), gpcrondump does a few validations and checks to see if the backup would be successful. Only if all the checks pass, does the actual DB dump start using gp_dump.
gpcrondump has been setup to send out emails whenever it fails (or succeeds, too). In a few cases, it would not send out an email even there is a failure. As stated in the Overview section, gpcrondump does a few checks before calling gp_dump to start the database backup. gpcrondump would terminate the program if it fails on one of the pre-checks and would not send an email about the failure. Only when gpcrondump fails during gp_dump, would it send an email.
The following would be the error in
20160607:20:00:30:180930 gpcrondump:test_server:gpadmin-[ERROR]:- Traceback (most recent call last): File "/usr/local/greenplum-db/lib/python/gppylib/commands/base.py", line 211, in run self.cmd.run() File "/usr/local/greenplum-db/lib/python/gppylib/operations/__init__.py", line 49, in run self.ret = self.execute() File "/usr/local/greenplum-db/lib/python/gppylib/operations/utils.py", line 52, in execute raise ret DumpDirCreateFailed 20160607:20:00:30:180930 gpcrondump:test_server:gpadmin-[ERROR]:-Could not create /isilon/dst/schema on sdw1.gphd.local.
gpcrondump failures during prerequisite checks do not send an email as the email routine is only called after the pre-checks are completed and the actual data dump is called using gp_dump. Any failures during the actual data dump would initiate an email whereas during pre-checks, gpcrondump is just terminated and hence no email is sent.
This is the way the product works. A feature request has been submitted and tracked in JIRA MPP-26416.