Troubleshoot Email Notification Channels

Symptom:
dxp10
Symptom:
Email notifications are not received.
Solution:
Follow these steps:
  1. Verify that the SMTP Server details are configured in the environment.
    1. Check the database for the SMTP server configuration. Ensure that the
      KeyValue, Name, URL (hostname:port), and
      Account
      (only when authentication is required) details are correctly updated in the database.
      select * from mcc_notify_service_provider where name like '%SystemProvider%';
      SMTPSettings.PNG
    2. If the SMTP configuration is not found, then update the database with the SMTP configuration using the DB Util.
      1. Edit the
        ServiceProviderEncryptReq.json
        file with the provider details in your deployment.
      2. Ensure that
        cryptojce-6.1.jar
        ,
        cryptojcommon-6.1.jar,
        and
        jcmFIPS-6.1.jar
        are available in the same directory as
        DBPopulator.jar
        .
      3. If running in Linux, add the following option to the following command:
        -Djava.security.egd=file:/dev/./urandom
        java -jar DBPopulator.jar -d postgresql -u <dbuser> -p <dbpwd> -n <PostgreSQLDatabaseName> -T E -e S -i ServiceProviderEncryptReq.json --host <db host> --port <db port>
        The following code is an example. Use your SMTP server details and credentials:
        { "encrypted": { "credential":"<SMTPAccount_Password>" }, "plain": { "keylevel":"-1", "keyvalue":"--GLOBALORGANIZATION--", "name":"SystemProvider", "protocol":"SMTP", "url":"smtps://<SMTPURL>", "account":"<SMTPAccount>", "options":"\"mail.smtp.dsn.notify\":\"SUCCESS,FAILURE,DELAY\",\"mail.smtp.dsn.ret\":\"FULL\""} } ]
      4. Ensure that the specified SMTP server is reachable from the
        axa-readserver
        pod.
  2. Verify if the alarms are being populated in the following indices:
    • http://<ElasticSearch url>/*channel*/_search?pretty&size=100
    • http://<ElasticSearch url>/*apm*/_search?pretty&size=100
    • http://<ElasticSearch URL>/*all_alarms*/_search?pretty&size=100
    If you do not see the data, then check if the pods are up and running. If all the pods are running and still no data in the indices, verify if the DX APM is generating the alerts. Also verify if the OI integration is working fine.
  3. In Kubernetes, validate if the Policy Manager and notify filter processes are up and running.
    1. Run
      ps -ef
      in the
      notify-filter
      deployment and look for the processes as shown in the following image:
      NotifyFilter_Troubleshooting.PNG If the processes are not up and running, restart the
      notify-filter
      pod and verify.
    2. Check the message templates sender address that should be accepted by the configured Email server. If not, update according to the email server.
      select sender,replyto from mcc_notify_msg_template