Table of Contents Previous Next


8 Notifications

Please note: For EDB Ark notifications to function properly, you must have an SMTP server running on each node, and specify the administrator’s email address in the ppcd.properties file and the cluster owner’s email address in the Ark console.
The MASTER|REPLICA database server dns_name in cluster cluster_name is now STOPPED|STARTING|RUNNING|WARNING|UNKNOWN in location availability_zone.
The MASTER|REPLICA database server dns_name in cluster cluster_name in location availability_zone is reporting an error determining the load balancer port.
The MASTER|REPLICA database server dns_name in cluster cluster_name is now RUNNING|STARTING|STOPPED|WARNING|UNKNOWN in location availability_zone using port port_number.
Continuous Archiving on the master|replica database server dns_name in cluster cluster_name is operating normally.
A problem was detected with continuous archiving on the master|replica database server dns_name in cluster cluster_name.
Data storage is being added to cluster cluster_name because the auto-scaling threshold was reached.
Data storage scaling for cluster cluster_name has been suspended
Data storage scaling for cluster cluster_name has been suspended. Instance instance_id no assignable device names left
The primary server, node id instance_id in cluster cluster_name is being rebuilt.
The primary server, node id instance_id in cluster cluster_name is being replaced with node id instance_id.
The replica server, node id instance_id in cluster cluster_name is being rebuilt.
Replica promotion failed. Node id: instance_id
WARNING: The EDB Ark cluster manager was unable to connect to the node manager for instance ID region/instance_id. This may be due to a temporary connectivity issue or the instance may require manual intervention.
The automatic|manual backup of cluster cluster_name in location availability_zone failed.
Backup of cluster cluster_name failed
The automatic|manual backup of cluster cluster_name in location availability_zone failed.
A storage container (bucket) named bucket_name has been created.
All EDB Ark clusters configured for Continuous Archiving (Point-in-Time Recovery) will use this location to store archived WAL files.
This container should not be deleted once created as it will cause WAL archiving to stop functioning.
Termination of cluster cluster_name completed.
The termination of cluster cluster_name has completed.
The system was not able to terminate instance {0} in cluster cluster_name because termination protection is enabled. You must disable termination protection before this instance can be terminated.
Yum update results for node: dns_name
Yum exit status:
exit_status
You may also consult the yum log on the node (usually in
/var/log/yum.log)
If there were any errors, you will have to log into the node and manually correct them and/or consult with your EDB Ark Admin.
Yum update results for node: dns_name
Yum exit status:
exit_status
You may also consult the yum log on the node (usually in
/var/log/yum.log) If there were any errors, you will have to log into the node and manually correct them and/or consult with your EDB Ark Admin
The OS/SW status on node dns_name of cluster cluster_name is now CRITICAL. This indicates that the node has at least one outstanding security update and possibly other non-critical updates available.
Please log into the EDB Ark console and perform a cluster upgrade.
The OS/SW status on node dns_name of cluster cluster_name is now UNKNOWN. This indicates that the node is having difficulty determining the OS/SW status.
This may be a temporary issue that will resolve itself. Please log into the EDB Ark console and check your cluster's status. If it is still showing status UNKNOWN then you will need to log into node
dns_name and run "yum --security check-update" to diagnose the issue manually.
The system was not able to delete the Security Group named group_name in cluster cluster_name. This could be because one or more instances in the cluster could not be terminated. This Security Group will need to be manually deleted from the provider's management console.
Reboot of cluster cluster_name in progress

8 Notifications

Table of Contents Previous Next