Pivotal Knowledge Base

Follow

GP failed to send log alert to email address: Access denied: 530

Environment 

Product Version
Pivotal Greenplum (GPDB)  4.3.x
OS  All
Others  

Symptom
The customer found that Greenplum cannot send an email alert to the DBA, while gpcrondump is sending an email.

Error Message:

2016-07-28 12:16:43.612927 HKT,"gpadmin","gpadmin",p15572,th796645152,"[local]",,2016-07-28 12:16:43 HKT,64883574,con346168,,seg-1,,,x64883574,sx1,"FATAL","3D000","database ""gpadmin"" does not exist",,,,,,,0,,"postinit.c",738, 
2016-07-28 12:16:43.613090 HKT,,,p25888,th796645152,,,,0,,,seg-1,,,,,"LOG","00000","Retrying emails now...",,,,,,,,"send_alert_via_email","cd ",556,
2016-07-28 12:16:48.638865 HKT,,,p25888,th796645152,,,,0,,,seg-1,,,,,"LOG","00000","could not send alert email to ""xxx@xxx.com""","Access denied: 530",,,,,,,"send_alert_via_email","sendalert.c",731,
2016-07-28 12:16:53.653180 HKT,,,p25888,th796645152,,,,0,,,seg-1,,,,,"LOG","00000","could not send alert email to ""xxx@xxx.com""","Access denied: 530",,,,,,,"send_alert_via_email","sendalert.c",731

Cause

GPDB email alert uses the SMTP server defined by GUC gp_email_smtp_server to send emails, while gpcrondump email uses the system-level SMTP server set in mail.rc file.

So the reason why this issue happens possibly be that they use different SMTP servers, amongst which the mail server is configured for sending mail alert has got some network configuration that refuses connection from the master.

Resolution

  1. Check the value of GUC gp_email_smtp_server:
    gpconfig -s gp_email_smtp_server
    
  2. Check the mail.rc (usually /etc/mail.rc) for the SMTP server set on system level

  3. If the two SMTP servers are not the same, actions below can be taken:
    1) Confirm with the customer whether we can replace the value of the GUC gp_email_smtp_server with the SMTP server set in mail.rc file.
    2) Ask the customers to check the network configuration like a firewall or the mail server originally defined in GUC gp_email_smtp_server. 

Comments

Powered by Zendesk