Resolving notification issues

Owned by Copy Space for Confluence
Jan 22, 2017
1 min read

If notifications are not being received or are not being sent, this could be due to a number of issues such as:

  • Mail server issues
  • Network issues
  • Email client issues

First of all double check all the mail configuration variables. Use the following commands to show all relevant variables.

dbvrep> show mailcfg
dbvrep> show notify
dbvrep> show _notify

Note the difference between global and per-process values (see Configuration Variable Reference for details). 

When turning on SMTP or SNMP notifications in Setup Wizard, per-process values are set for most of the notification variables. Because of that your global values may be ignored.


For more information on notifications, please see Notifications and Remote Management

In order to debug the notifications please follow these steps:

APPLY process

dbvrep> set APPLY._NOTIFY_VERBOSE_DEBUG=1
dbvrep> set APPLY._NETWORK_TRAFFIC_DEBUG=1


Restart the APPLY process, then reproduce the issue to send the notification and inspect the APPLY log on the APPLY process.

MINE process

The same can be done for the MINE process:

dbvrep> set MINE._NOTIFY_VERBOSE_DEBUG=1
dbvrep> set MINE._NETWORK_TRAFFIC_DEBUG=1


Restart the MINE process.

Both MINE and APPLY processes

dbvrep> set _NOTIFY_VERBOSE_DEBUG=1
dbvrep> set _NETWORK_TRAFFIC_DEBUG=1


Restart both MINE and APPLY processes for these settings to take affect.

Send Notification

To manually send a test notification use the following command:

dbvrep>notify send daily_progress
dbvrep>notify send heartbeat