Notifications v3

Edit this page

Failover Manager will send e-mail notifications and/or invoke a notification script when a notable event occurs that affects the cluster. If you have configured Failover Manager to send an email notification, you must have an SMTP server running on port 25 on each node of the cluster. Use the following parameters to configure notification behavior for Failover Manager:

user.email
script.notification
from.email

For more information about editing the configuration properties, see Specifying Cluster Properties.

The body of the notification contains details about the event that triggered the notification, and about the current state of the cluster. For example:

EFM node: 10.0.1.11
Cluster name: acctg
Database name: postgres
VIP: ip_address (Active|Inactive)
Database health is not being monitored.

The VIP field displays the IP address and state of the virtual IP if implemented for the node.

Failover Manager assigns a severity level to each notification. The following levels indicate increasing levels of attention required:

  • INFO indicates an informational message about the agent and does not require any manual intervention (for example, Failover Manager has started or stopped). See List of INFO level notifications
  • WARNING indicates that an event has happened that requires the administrator to check on the system (for example, failover has occurred). See List of WARNING level notifications
  • SEVERE indicates that a serious event has happened and requires the immediate attention of the administrator (for example, failover was attempted, but was unable to complete). See List of SEVERE level notifications

The severity level designates the urgency of the notification. A notification with a severity level of SEVERE requires user attention immediately, while a notification with a severity level of INFO will call your attention to operational information about your cluster that does not require user action. Notification severity levels are not related to logging levels; all notifications are sent regardless of the log level detail specified in the configuration file.

You can use the notification.level property to specify the minimum severity level that will trigger a notification.

Note

In addition to sending notices to the administrative email address, all notifications are recorded in the cluster log file (/var/log/efm-3.10/<cluster_name>.log).

The conditions listed in the table below will trigger an INFO level notification:

SubjectDescription
Executed fencing scriptExecuted fencing script script_name Results: script_results
Executed post-promotion scriptExecuted post-promotion script script_name Results: script_results
Executed remote pre-promotion scriptExecuted remote pre-promotion script script_name Results: script_results
Executed remote post-promotion scriptExecuted remote post-promotion script script_name Results: script_results
Executed post-database failure scriptExecuted post-database failure script script_name Results: script_results
Executed primary isolation scriptExecuted primary isolation script script_name Results: script_results
Witness agent running on node_address for cluster cluster_nameWitness agent is running.
Primary agent running on node_address for cluster cluster_namePrimary agent is running and database health is being monitored.
Standby agent running on node_address for cluster cluster_nameStandby agent is running and database health is being monitored.
Idle agent running on node node_address for cluster cluster_nameIdle agent is running. After starting the local database, the agent can be resumed.
Assigning VIP to node node_addressAssigning VIP VIP_address to node node_address Results: script_results
Releasing VIP from node node_addressReleasing VIP VIP_address from node node_address Results: script_results
Starting auto resume check for cluster cluster_nameThe agent on this node will check every auto.resume.period seconds to see if it can resume monitoring the failed database. The cluster should be checked during this time and the agent stopped if the database will not be started again. See the agent log for more details.
Executed agent resumed scriptExecuted agent resumed script script_name Results: script_results
WAL logs backed up during promotionWhen reconfiguring this standby to follow the new primary, the pg_xlog or pg_wal contents were backed up in the pgdata directory. This backup should be removed when convenient to free up disk space.

The conditions listed in the table below will trigger a WARNING level notification:

SubjectDescriptionComments
Witness agent exited on node_address for cluster cluster_nameWitness agent has exited.
Primary agent exited on node_address for cluster cluster_nameDatabase health is not being monitored.
Cluster cluster_name notified that primary node has leftFailover is disabled for the cluster until the primary agent is restarted.
Standby agent exited on node_address for cluster cluster_nameDatabase health is not being monitored.
Agent exited during promotion on node_address for cluster cluster_nameDatabase health is not being monitored.
Agent exited on node_address for cluster cluster_nameThe agent has exited. This is generated by an agent in the Idle state.
Agent exited for cluster cluster_nameThe agent has exited. This notification is usually generated during startup when an agent exits before startup has completed.
Virtual IP address assigned to non-primary nodeThe virtual IP address appears to be assigned to a non-primary node. To avoid any conflicts, Failover Manager will release the VIP. You should confirm that the VIP is assigned to your primary node and manually reassign the address if it is not.
Virtual IP address not assigned to primary nodeThe virtual IP address appears to not be assigned to a primary node. EDB Postgres Failover Manager will attempt to reacquire the VIP.
No standby agent in cluster for cluster cluster_nameThe standbys on cluster_name have left the cluster.
Standby agent failed for cluster cluster_nameA standby agent on cluster_name has left the cluster, but the coordinator has detected that the standby database is still running.
Standby database failed for cluster cluster_nameA standby agent has signaled that its database has failed. The other nodes also cannot reach the standby database.
Standby agent cannot reach database for cluster cluster_nameA standby agent has signaled database failure, but the other nodes have detected that the standby database is still running.
Cluster cluster_name has dropped below three nodesAt least three nodes are required for full failover protection. Please add witness or agent node to the cluster.
Subset of cluster cluster_name disconnected from primaryThis node is no longer connected to the majority of the cluster cluster_name. Because this node is part of a subset of the cluster, failover will not be attempted. Current nodes that are visible are: node_address
Promotion has started on cluster cluster_nameThe promotion of a standby has started on cluster cluster_name.
Witness failure for cluster cluster_nameWitness running at node_address has left the cluster.
Idle agent failure for cluster cluster_nameIdle agent running at node_address has left the cluster.
One or more nodes isolated from network for cluster cluster_nameThis node appears to be isolated from the network. Other members seen in the cluster are: node_name
Node no longer isolated from network for cluster cluster_name.This node is no longer isolated from the network.
Standby agent tried to promote, but primary DB is still runningThe standby EFM agent tried to promote itself, but detected that the primary DB is still running on node_address. This usually indicates that the primary EFM agent has exited. Failover has NOT occurred.
Standby agent started to promote, but primary has rejoined.The standby EFM agent started to promote itself, but found that a primary agent has rejoined the cluster. Failover has NOT occurred.
Standby agent tried to promote, but could not verify primary DBThe standby EFM agent tried to promote itself, but could not detect whether or not the primary DB is still running on node_address. Failover has NOT occurred.
Standby agent tried to promote, but VIP appears to still be assignedThe standby EFM agent tried to promote itself, but could not because the virtual IP address (VIP_address) appears to still be assigned to another node. Promoting under these circumstances could cause data corruption. Failover has NOT occurred.
Standby agent tried to promote, but appears to be orphanedThe standby EFM agent tried to promote itself, but could not because the well-known server (server_address) could not be reached. This usually indicates a network issue that has separated the standby agent from the other agents. Failover has NOT occurred.
Failover has not occurredAn agent has detected that the master database is no longer available in cluster cluster_name, but there are no standby nodes available for failover.
Potential manual failover required on cluster cluster_nameA potential failover situation was detected for cluster cluster_name. Automatic failover has been disabled for this cluster, so manual intervention is required.
Failover has completed on cluster cluster_nameFailover has completed on cluster cluster_name.
Lock file for cluster cluster_name has been removedThe lock file for cluster cluster_name has been removed from: path_name on node node_address. This lock prevents multiple agents from monitoring the same cluster on the same node. Please restore this file to prevent accidentally starting another agent for cluster.
A recovery file for cluster cluster_name has been found on primary nodeA recovery file for cluster cluster_name has been found at: path_name on primary node node_address. This may be problematic should you attempt to restart the DB on this node.
recovery_target_timeline is not set to latest in recovery settingsThe recovery_target_timeline parameter is not set to latest in the recovery settings. The standby server will not be able to follow a timeline change that occurs when a new primary is promoted.
trigger_file path given in recovery.conf is not writableThe path provided for the trigger_file parameter in the recovery.conf file is not writable by the db_service_owner user. Failover Manager will not be able to promote the database if needed.Not available in EFM 3.10.
Promotion has not occurred for cluster cluster_nameA promotion was attempted but there is already a node being promoted: ip_address.
Standby not reconfigured after failover in cluster cluster_nameThe auto.reconfigure property has been set to false for this node. The node has not been reconfigured to follow the new primary node after a failover.
Could not resume replay for cluster cluster_nameCould not resume replay for standby being promoted. Manual intervention may be required. Error: error_description This error is returned if the server encounters an error when invoking replay during the promotion of a standby.
Could not resume replay for standby standby_idCould not resume replay for standby. Manual intervention may be required. Error: error_message.
Possible problem with database timeout valuesYour remote.timeout value (value) is higher than your local.timeout value (value). If the local database takes too long to respond, the local agent could assume that the database has failed though other agents can connect. While this will not cause a failover, it could force the local agent to stop monitoring, leaving you without failover protection.
No standbys available for promotion in cluster cluster_nameThe current number of standby nodes in the cluster has dropped to the minimum number: number. There cannot be a failover unless another standby node(s) is added or made promotable.
No promotable standby for cluster cluster_nameThe current failover priority list in the cluster is empty. You have removed the only promotable standby for the cluster cluster_name. There cannot be a failover unless another promotable standby node(s) is added or made promotable by adding to failover priority list.Available in EFM 3.9 and later.
Synchronous replication has been disabled for cluster cluster_nameThe number of synchronous standby nodes in the cluster has dropped below count. The primary has been taken out of synchronous replication mode.
Could not reload database configuration.Could not reload database configuration. Manual intervention is required. Error: error_message.
Custom monitor timeout for cluster cluster_nameThe following custom monitoring script has timed out: script_name
Custom monitor 'safe mode' failure for cluster cluster_nameThe following custom monitor script has failed, but is being run in "safe mode": script_name. Output: script_results

The conditions listed in the table below will trigger a SEVERE notification:

SubjectDescriptionNotes
Standby database restarted but EFM cannot connectThe start or restart command for the database ran successfully but the database is not accepting connections. EFM will keep trying to connect for up to restart.connection.timeout seconds.
Unable to connect to DB on node_addressThe maximum connections limit has been reached.
Unable to connect to DB on node_addressInvalid password for db.user=user_name.
Unable to connect to DB on node_addressInvalid authorization specification.
Master cannot ping local database for cluster cluster_nameThe primary agent can no longer reach the local database running at node_address. Other nodes are able to access the database remotely, so the primary will not release the VIP and/or create a recovery.conf file. The primary agent will remain IDLE until the resume command is run to resume monitoring the database.
Fencing script errorFencing script script_name failed to execute successfully. Exit Value: exit_code Results: script_results Failover has NOT occurred.
Post-promotion script failedPost-promotion script script_name failed to execute successfully. Exit Value: exit_code Results: script_results
Remote post-promotion script failedRemote post-promotion script script_name failed to execute successfully Exit Value: exit_code Results: script_resultsNode: node_address
Remote pre-promotion script failedRemote pre-promotion script script_name failed to execute successfully Exit Value: exit_code Results: script_resultsNode: node_address
Post-database failure script errorPost-database failure script script_name failed to execute successfully. Exit Value: exit_code Results: script_results
Agent resumed script errorAgent resumed script script_name failed to execute successfully. Results: script_results
Primary isolation script failedPrimary isolation script script_name failed to execute successfully. Exit Value: exit_code Results: script_results
Could not promote standbyThe promote command failed on node. Could not promote standby. Error details: error_detailsDescription applicable to EFM 3.10.
Could not promote standbyThe trigger file file_name could not be created on node. Could not promote standby. Error details: message_detailsDescription applicable to EFM 3.9 and earlier.
Error creating recovery.conf file on node_address for cluster cluster_nameThere was an error creating the recovery.conf file on primary node node_address during promotion. Promotion has continued, but requires manual intervention to ensure that the old primary node can not be restarted. Error details: message_details
An unexpected error has occurred for cluster cluster_nameAn unexpected error has occurred on this node. Please check the agent log for more information. Error: error_details
Primary database being fenced off for cluster cluster_nameThe primary database has been isolated from the majority of the cluster. The cluster is telling the primary agent at ip_address to fence off the primary database to prevent two primarys when the rest of the failover manager cluster promotes a standby.
Isolated primary database shutdown.The isolated primary database has been shutdown by failover manager.
Primary database being fenced off for cluster cluster_nameThe primary database has been isolated from the majority of the cluster. Before the primary could finish detecting isolation, a standby was promoted and has rejoined this node in the cluster. This node is isolating itself to avoid more than one primary database.
Could not assign VIP to node node_addressFailover manager could not assign the VIP address for some reason.
primary_or_standby database failure for cluster cluster_nameThe database has failed on the specified node.
Agent is timing out for cluster cluster_nameThis agent has timed out trying to reach the local database. After the timeout, the agent could successfully ping the database and has resumed monitoring. However, the node should be checked to make sure it is performing normally to prevent a possible database or agent failure.
Resume timed out for cluster cluster_nameThis agent could not resume monitoring after reconfiguring and restarting the local database. See agent log for details.
Internal state mismatch for cluster cluster_nameThe failover manager cluster's internal state did not match the actual state of the cluster members. This is rare and can be caused by a timing issue of nodes joining the cluster and/or changing their state. The problem should be resolved, but you should check the cluster status as well to verify. Details of the mismatch can be found in the agent log file.
Failover has not occurredAn agent has detected that the primary database is no longer available in cluster cluster_name, but there are no standby nodes available for failover.
Database in wrong state on node_addressThe standby agent has detected that the local database is no longer in recovery. The agent will now become idle. Manual intervention is required.
Database in wrong state on node_addressThe primary agent has detected that the local database is in recovery. The agent will now become idle. Manual intervention is required.
Database connection failure for cluster cluster_nameThis node is unable to connect to the database running on: node_addressUntil this is fixed, failover may not work properly because this node will not be able to check if the database is running or not.
Standby custom monitor failure for cluster cluster_nameThe following custom monitor script has failed on a standby node. The agent will stop monitoring the local database. Script location: script_name Script output: script_results
master.shutdown.as.failure set to true for master nodeThe master.shutdown.as.failure property has been set to true for this cluster. Stopping the primary agent without stopping the entire cluster will be treated by the rest of the cluster as an immediate primary agent failure. If maintenance is required on the primary database, shut down the primary agent and wait for a notification from the remaining nodes that failover will not happen.
Primary custom monitor failure for cluster cluster_nameThe following custom monitor script has failed on a primary node. EFM will attempt to promote a standby. Script location: script_name Script output: script_results
Loopback address set for ping.server.ipLoopback address is set for ping.server.ip property. This setting can interfere with the network isolation detection and hence it should be changed.Available in EFM 3.10
Load balancer attach script errorLoad balancer attach script script_name failed to execute successfully. Exit Value: exit_code Results: script_results
Load balancer detach script errorLoad balancer detach script script_name failed to execute successfully. Exit Value: exit_code Results: script_results
Not enough synchronous standbys available in cluster cluster_name.The number of synchronous standby nodes in the cluster has dropped to count. All write queries on the primary will be blocked until enough synchronous standby nodes are added.Changed from WARNING to SEVERE in EFM 3.9.