{"id":11006,"date":"2018-03-07T16:31:27","date_gmt":"2018-03-07T15:31:27","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/"},"modified":"2023-06-09T16:54:26","modified_gmt":"2023-06-09T14:54:26","slug":"edb-failover-manager-3-0-and-postgresql-10-1","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/","title":{"rendered":"EDB Failover Manager 3.0 and PostgreSQL 10.1"},"content":{"rendered":"

By Mouhamadou Diaw<\/strong><\/p>\n

Edb Failover Manager edb-efm30 is now released and supports PostgreSQL 10.1.
\nEfm is an EDB tool which can be used to perform a switchover and a failover in a PostgreSQL standby environment.
\nIn this blog we are going to see how we can install and configure efm in a standby environment. We suppose that the standby is already confugured and is running. We also have not configured any VIP. I just use 3 virtual machines to test. Below the configuration we are using 3 servers with Oracle Linux 7.2<\/p>\n

pgservertools: 192.168.56.30 which is the witness
\npgserver1: 192.168.56.36 which is the primary server
\npgserver2: 192.168.56.37 which is the standby
\n\"config\"<\/a>
\nEFM must be installed on both 3 nodes.To install EDB EFM,I used the rpm provided by EnterpriseDB. Note that you will need an Edb account.We will show the installation on only one node, but is the same for both nodes.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n<\/td>\n
\n
\n
[root@host tmp]<\/code># wget http:\/\/yum.enterprisedb.com\/edbrepos\/edb-repo-latest.noarch.rpm<\/a><\/code><\/div>\n
[root@host tmp]<\/code># yum localinstall -y edb-repo-latest.noarch.rpm<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

After we have to enable the corresponding edb repository (You will need a login and password)<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n<\/td>\n
\n
\n
[root@pgservertools yum.repos.d]<\/code># cat \/etc\/yum.repos.d\/edb.repo<\/code><\/div>\n
[edbas10]<\/code><\/div>\n
name=EnterpriseDB Advanced Server 10 $releasever - $basearch<\/code><\/div>\n
baseurl=http:<\/code>\/\/login<\/code>:password@yum.enterprisedb.com<\/code>\/10\/redhat\/rhel-<\/code>$releasever-$basearch<\/code><\/div>\n
enabled=1<\/code><\/div>\n
gpgcheck=1<\/code><\/div>\n
gpgkey=<\/code>file<\/code>:<\/code>\/\/\/etc\/pki\/rpm-gpg\/ENTERPRISEDB-GPG-KEY<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And then we can search for the package<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n<\/td>\n
\n
\n
[root@pgservertools ~]<\/code># yum search efm<\/code><\/div>\n
Loaded plugins: langpacks, ulninfo<\/code><\/div>\n
=============================== N<\/code>\/S<\/code> matched: efm ===============================<\/code><\/div>\n
edb-efm30.x86_64 : EnterpriseDB Failover Manager<\/code><\/div>\n
efm20.x86_64 : EnterpriseDB Failover Manager<\/code><\/div>\n
efm21.x86_64 : EnterpriseDB Failover Manager<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And then install it (ouputs are truncated)<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n<\/td>\n
\n
\n
[root@pgservertools ~]<\/code># yum install edb-efm30.x86_64<\/code><\/div>\n
Loaded plugins: langpacks, ulninfo<\/code><\/div>\n
Resolving Dependencies<\/code><\/div>\n
--> Running transaction check<\/code><\/div>\n
---> Package edb-efm30.x86_64 0:3.0.0-1.rhel7 will be installed<\/code><\/div>\n
--> Finished Dependency Resolution<\/code><\/div>\n
\u2026<\/code><\/div>\n
\u2026<\/code><\/div>\n
Installed:<\/code><\/div>\n
\u00a0\u00a0<\/code>edb-efm30.x86_64 0:3.0.0-1.rhel7<\/code><\/div>\n
Complete!<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

efm requires also openjdk. So we also have installed openjdk 1.8 on all nodes:<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n<\/td>\n
\n
\n
root@host tmp]<\/code># yum install java-1.8.0-openjdk.x86_64<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

To manage efm we create a dedicated user in the primary cluster<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n<\/td>\n
\n
\n
postgres=<\/code># create user efm with login password 'root' superuser;<\/code><\/div>\n
CREATE ROLE<\/code><\/div>\n
postgres=<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

We have to add following entries to pg_hba.conf of all databases clusters to allow connection for user efm.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
##for efm<\/code><\/div>\n
host\u00a0 postgres\u00a0\u00a0\u00a0 efm\u00a0 192.168.56.36<\/code>\/32<\/code>\u00a0\u00a0\u00a0\u00a0 md5<\/code><\/div>\n
host\u00a0 postgres\u00a0\u00a0\u00a0 efm\u00a0 192.168.56.37<\/code>\/32<\/code>\u00a0\u00a0\u00a0\u00a0 md5<\/code><\/div>\n
host\u00a0 postgres\u00a0\u00a0\u00a0 efm\u00a0 192.168.56.30<\/code>\/32<\/code>\u00a0\u00a0\u00a0\u00a0 md5<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

The configuration of efm consists of editing 2 main configuration files: efm.nodes<\/strong> and efm.properties<\/strong>. In my case these files are located in \/etc\/edb\/efm-3.0. There are already two sample files that we can copy and then edit.
\nFirst we need to encrypt the password of user efm and after we have to configure efm.nodes and efm.properties on both nodes.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n<\/td>\n
\n
\n
[root@pgserver1 efm-3.0]<\/code># \/usr\/edb\/efm-3.0\/bin\/efm encrypt efm<\/code><\/div>\n
This utility will generate an encrypted password <\/code>for<\/code> you to place <\/code>in<\/code> your<\/code><\/div>\n
EFM cluster property <\/code>file<\/code>.<\/code><\/div>\n
Please enter the password and hit enter:<\/code><\/div>\n
Please enter the password again to confirm:<\/code><\/div>\n
The encrypted password is: ff7f041651e5e864013c1102d26a5e08<\/code><\/div>\n
Please <\/code>paste<\/code> this into your cluster properties <\/code>file<\/code>.<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>db.password.encrypted= ff7f041651e5e864013c1102d26a5e08<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Below we show the contents of our two configuration files
\nOn pgserver1 which is the primary<\/strong>
\nefm.nodes<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n<\/td>\n
\n
\n
root@pgserver1 101]<\/code># cat \/etc\/edb\/efm-3.0\/efm.nodes<\/code><\/div>\n
# List of node address:port combinations separated by whitespace.<\/code><\/div>\n
# The list should include at least the membership coordinator's address.<\/code><\/div>\n
192.168.56.30:9998 192.168.56.37:9998<\/code><\/div>\n
[root@pgserver1 101]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

efm.properties<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n
28<\/div>\n
29<\/div>\n
30<\/div>\n
31<\/div>\n
32<\/div>\n
33<\/div>\n
34<\/div>\n
35<\/div>\n
36<\/div>\n
37<\/div>\n
38<\/div>\n
39<\/div>\n
40<\/div>\n
41<\/div>\n
42<\/div>\n
43<\/div>\n
44<\/div>\n
45<\/div>\n
46<\/div>\n
47<\/div>\n
48<\/div>\n
49<\/div>\n<\/td>\n
\n
\n
[root@pgserver1 101]<\/code># cat \/etc\/edb\/efm-3.0\/efm.properties | grep -v ^#<\/code><\/div>\n
db.user=efm<\/code><\/div>\n
db.password.encrypted=ff7f041651e5e864013c1102d26a5e08<\/code><\/div>\n
db.port=5436<\/code><\/div>\n
db.database=postgres<\/code><\/div>\n
db.service.owner=postgres<\/code><\/div>\n
db.service.name=<\/code><\/div>\n
db.bin=<\/code>\/u01\/app\/postgres\/product\/10\/db_1\/bin<\/code><\/div>\n
db.recovery.conf.<\/code>dir<\/code>=<\/code>\/u90\/mydata\/101<\/code><\/div>\n
jdbc.sslmode=disable<\/code><\/div>\n
user.email=xxx@xxx.fr<\/code><\/div>\n
script.notification=<\/code><\/div>\n
bind.address=192.168.56.36:9998<\/code><\/div>\n
admin.port=9999<\/code><\/div>\n
is.witness=<\/code>false<\/code><\/div>\n
local<\/code>.period=10<\/code><\/div>\n
local<\/code>.timeout=60<\/code><\/div>\n
local<\/code>.timeout.final=10<\/code><\/div>\n
remote.timeout=10<\/code><\/div>\n
node.timeout=50<\/code><\/div>\n
stop.isolated.master=<\/code>false<\/code><\/div>\n
pingServerIp=192.168.56.30<\/code><\/div>\n
pingServerCommand=<\/code>\/bin\/ping<\/code> -q -c3 -w5<\/code><\/div>\n
auto.allow.hosts=<\/code>false<\/code><\/div>\n
db.reuse.connection.count=0<\/code><\/div>\n
auto.failover=<\/code>true<\/code><\/div>\n
auto.reconfigure=<\/code>true<\/code><\/div>\n
promotable=<\/code>true<\/code><\/div>\n
minimum.standbys=0<\/code><\/div>\n
recovery.check.period=2<\/code><\/div>\n
auto.resume.period=0<\/code><\/div>\n
script.fence=<\/code><\/div>\n
script.post.promotion=<\/code><\/div>\n
script.resumed=<\/code><\/div>\n
script.db.failure=<\/code><\/div>\n
script.master.isolated=<\/code><\/div>\n
script.remote.pre.promotion=<\/code><\/div>\n
script.remote.post.promotion=<\/code><\/div>\n
script.custom.monitor=<\/code><\/div>\n
custom.monitor.interval=<\/code><\/div>\n
custom.monitor.timeout=<\/code><\/div>\n
custom.monitor.safe.mode=<\/code><\/div>\n
sudo<\/code>.<\/code>command<\/code>=<\/code>sudo<\/code><\/div>\n
sudo<\/code>.user.<\/code>command<\/code>=<\/code>sudo<\/code> -u %u<\/code><\/div>\n
log.<\/code>dir<\/code>=<\/code>\/var\/log\/efm-3<\/code>.0<\/code><\/div>\n
jgroups.loglevel=INFO<\/code><\/div>\n
efm.loglevel=INFO<\/code><\/div>\n
jvm.options=-Xmx32m<\/code><\/div>\n
[root@pgserver1 101]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

On pgserver2 which is the standby<\/strong>
\nefm.nodes<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n<\/td>\n
\n
\n
[root@pgserver2 tmp]<\/code># cat \/etc\/edb\/efm-3.0\/efm.nodes<\/code><\/div>\n
# List of node address:port combinations separated by whitespace.<\/code><\/div>\n
# The list should include at least the membership coordinator's address.<\/code><\/div>\n
192.168.56.30:9998 192.168.56.36:9998<\/code><\/div>\n
[root@pgserver2 tmp]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

efm.properties<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n
28<\/div>\n
29<\/div>\n
30<\/div>\n
31<\/div>\n
32<\/div>\n
33<\/div>\n
34<\/div>\n
35<\/div>\n
36<\/div>\n
37<\/div>\n
38<\/div>\n
39<\/div>\n
40<\/div>\n
41<\/div>\n
42<\/div>\n
43<\/div>\n
44<\/div>\n
45<\/div>\n
46<\/div>\n
47<\/div>\n
48<\/div>\n
49<\/div>\n<\/td>\n
\n
\n
[root@pgserver2 tmp]<\/code># cat \/etc\/edb\/efm-3.0\/efm.properties | grep -v ^#<\/code><\/div>\n
db.user=efm<\/code><\/div>\n
db.password.encrypted=ff7f041651e5e864013c1102d26a5e08<\/code><\/div>\n
db.port=5436<\/code><\/div>\n
db.database=postgres<\/code><\/div>\n
db.service.owner=postgres<\/code><\/div>\n
db.service.name=<\/code><\/div>\n
db.bin=<\/code>\/u01\/app\/postgres\/product\/10\/db_1\/bin<\/code><\/div>\n
db.recovery.conf.<\/code>dir<\/code>=<\/code>\/u90\/mydata\/101<\/code><\/div>\n
jdbc.sslmode=disable<\/code><\/div>\n
user.email=xxx@xxx.fr<\/code><\/div>\n
script.notification=<\/code><\/div>\n
bind.address=192.168.56.37:9998<\/code><\/div>\n
admin.port=9999<\/code><\/div>\n
is.witness=<\/code>false<\/code><\/div>\n
local<\/code>.period=10<\/code><\/div>\n
local<\/code>.timeout=60<\/code><\/div>\n
local<\/code>.timeout.final=10<\/code><\/div>\n
remote.timeout=10<\/code><\/div>\n
node.timeout=50<\/code><\/div>\n
stop.isolated.master=<\/code>false<\/code><\/div>\n
pingServerIp=192.168.56.30<\/code><\/div>\n
pingServerCommand=<\/code>\/bin\/ping<\/code> -q -c3 -w5<\/code><\/div>\n
auto.allow.hosts=<\/code>true<\/code><\/div>\n
db.reuse.connection.count=0<\/code><\/div>\n
auto.failover=<\/code>true<\/code><\/div>\n
auto.reconfigure=<\/code>true<\/code><\/div>\n
promotable=<\/code>true<\/code><\/div>\n
minimum.standbys=0<\/code><\/div>\n
recovery.check.period=2<\/code><\/div>\n
auto.resume.period=0<\/code><\/div>\n
script.fence=<\/code><\/div>\n
script.post.promotion=<\/code><\/div>\n
script.resumed=<\/code><\/div>\n
script.db.failure=<\/code><\/div>\n
script.master.isolated=<\/code><\/div>\n
script.remote.pre.promotion=<\/code><\/div>\n
script.remote.post.promotion=<\/code><\/div>\n
script.custom.monitor=<\/code><\/div>\n
custom.monitor.interval=<\/code><\/div>\n
custom.monitor.timeout=<\/code><\/div>\n
custom.monitor.safe.mode=<\/code><\/div>\n
sudo<\/code>.<\/code>command<\/code>=<\/code>sudo<\/code><\/div>\n
sudo<\/code>.user.<\/code>command<\/code>=<\/code>sudo<\/code> -u %u<\/code><\/div>\n
log.<\/code>dir<\/code>=<\/code>\/var\/log\/efm-3<\/code>.0<\/code><\/div>\n
jgroups.loglevel=INFO<\/code><\/div>\n
efm.loglevel=INFO<\/code><\/div>\n
jvm.options=-Xmx32m<\/code><\/div>\n
[root@pgserver2 tmp]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

On pgservertools which is the witness<\/strong>
\nefm.nodes<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># cat \/etc\/edb\/efm-3.0\/efm.nodes<\/code><\/div>\n
# List of node address:port combinations separated by whitespace.<\/code><\/div>\n
# The list should include at least the membership coordinator's address.<\/code><\/div>\n
192.168.56.36:9998 192.168.56.37:9998<\/code><\/div>\n
[root@pgservertools efm-3.0]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

efm.properties<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n
28<\/div>\n
29<\/div>\n
30<\/div>\n
31<\/div>\n
32<\/div>\n
33<\/div>\n
34<\/div>\n
35<\/div>\n
36<\/div>\n
37<\/div>\n
38<\/div>\n
39<\/div>\n
40<\/div>\n
41<\/div>\n
42<\/div>\n
43<\/div>\n
44<\/div>\n
45<\/div>\n
46<\/div>\n
47<\/div>\n
48<\/div>\n
49<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># cat \/etc\/edb\/efm-3.0\/efm.properties | grep -v ^#<\/code><\/div>\n
db.user=efm<\/code><\/div>\n
db.password.encrypted=ff7f041651e5e864013c1102d26a5e08<\/code><\/div>\n
db.port=5436<\/code><\/div>\n
db.database=postgres<\/code><\/div>\n
db.service.owner=postgres<\/code><\/div>\n
db.service.name=<\/code><\/div>\n
db.bin=<\/code>\/u01\/app\/postgres\/product\/10\/db_1\/bin<\/code><\/div>\n
db.recovery.conf.<\/code>dir<\/code>=<\/code>\/u90\/mydata\/101<\/code><\/div>\n
jdbc.sslmode=disable<\/code><\/div>\n
user.email=xxx@xxx.fr<\/code><\/div>\n
script.notification=<\/code><\/div>\n
bind.address=192.168.56.30:9998<\/code><\/div>\n
admin.port=9999<\/code><\/div>\n
is.witness=<\/code>true<\/code><\/div>\n
local<\/code>.period=10<\/code><\/div>\n
local<\/code>.timeout=60<\/code><\/div>\n
local<\/code>.timeout.final=10<\/code><\/div>\n
remote.timeout=10<\/code><\/div>\n
node.timeout=50<\/code><\/div>\n
stop.isolated.master=<\/code>false<\/code><\/div>\n
pingServerIp=192.168.56.30<\/code><\/div>\n
pingServerCommand=<\/code>\/bin\/ping<\/code> -q -c3 -w5<\/code><\/div>\n
auto.allow.hosts=<\/code>false<\/code><\/div>\n
db.reuse.connection.count=0<\/code><\/div>\n
auto.failover=<\/code>true<\/code><\/div>\n
auto.reconfigure=<\/code>true<\/code><\/div>\n
promotable=<\/code>true<\/code><\/div>\n
minimum.standbys=0<\/code><\/div>\n
recovery.check.period=2<\/code><\/div>\n
auto.resume.period=0<\/code><\/div>\n
script.fence=<\/code><\/div>\n
script.post.promotion=<\/code><\/div>\n
script.resumed=<\/code><\/div>\n
script.db.failure=<\/code><\/div>\n
script.master.isolated=<\/code><\/div>\n
script.remote.pre.promotion=<\/code><\/div>\n
script.remote.post.promotion=<\/code><\/div>\n
script.custom.monitor=<\/code><\/div>\n
custom.monitor.interval=<\/code><\/div>\n
custom.monitor.timeout=<\/code><\/div>\n
custom.monitor.safe.mode=<\/code><\/div>\n
sudo<\/code>.<\/code>command<\/code>=<\/code>sudo<\/code><\/div>\n
sudo<\/code>.user.<\/code>command<\/code>=<\/code>sudo<\/code> -u %u<\/code><\/div>\n
log.<\/code>dir<\/code>=<\/code>\/var\/log\/efm-3<\/code>.0<\/code><\/div>\n
jgroups.loglevel=INFO<\/code><\/div>\n
efm.loglevel=INFO<\/code><\/div>\n
jvm.options=-Xmx32m<\/code><\/div>\n
[root@pgservertools efm-3.0]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Now let\u2019s start efm on both nodes. If there is any error check logs on \/var\/log\/efm-3.0\/.
\nI started on following order: pgserver1, pgserver2 and pgservertools. Services can be configured to be started automatically when the server starts.
\nBelow an example on pgserverools<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># service efm-3.0 start<\/code><\/div>\n
.<\/code><\/div>\n
[root@pgservertools efm-3.0]<\/code># service efm-3.0 status<\/code><\/div>\n
Redirecting to <\/code>\/bin\/systemctl<\/code> status\u00a0 efm-3.0.service<\/code><\/div>\n
\u25cf efm-3.0.service - EnterpriseDB Failover Manager 3.0<\/code><\/div>\n
\u00a0\u00a0\u00a0<\/code>Loaded: loaded (<\/code>\/usr\/lib\/systemd\/system\/efm-3<\/code>.0.service; disabled; vendor preset: disabled)<\/code><\/div>\n
\u00a0\u00a0\u00a0<\/code>Active: active (running) since Tue 2018-03-06 15:58:51 CET; 1h 46min ago<\/code><\/div>\n
\u00a0\u00a0<\/code>Process: 22260 ExecStart=<\/code>\/bin\/bash<\/code> -c <\/code>\/usr\/edb\/efm-3<\/code>.0<\/code>\/bin\/runefm<\/code>.sh start ${CLUSTER} (code=exited, status=0<\/code>\/SUCCESS<\/code>)<\/code><\/div>\n
\u00a0<\/code>Main PID: 22321 (java)<\/code><\/div>\n
\u00a0\u00a0\u00a0<\/code>CGroup: <\/code>\/system<\/code>.slice<\/code>\/efm-3<\/code>.0.service<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>\u2514\u250022321 <\/code>\/usr\/lib\/jvm\/java-1<\/code>.8.0-openjdk-1.8.0.151-1.b12.el7_4.x86_64<\/code>\/jre\/bin\/java<\/code> -<\/code>cp<\/code> \/usr\/edb\/efm-3<\/code>.0<\/code>\/lib\/EFM-3<\/code>.0.0.jar -Xmx32m com.enterprisedb.efm.main.ServiceCommand __int_start <\/code>\/e<\/code>...<\/code><\/div>\n
Mar 06 15:58:45 pgservertools.localdomain systemd[1]: Starting EnterpriseDB Failover Manager 3.0...<\/code><\/div>\n
Mar 06 15:58:51 pgservertools.localdomain systemd[1]: Started EnterpriseDB Failover Manager 3.0.<\/code><\/div>\n
[root@pgservertools efm-3.0]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Once started we can verified from any node the status of our cluster<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># \/usr\/edb\/efm-3.0\/bin\/efm cluster-status efm<\/code><\/div>\n
Cluster Status: efm<\/code><\/div>\n
VIP:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Agent Type\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Agent\u00a0 DB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Witness\u00a0\u00a0\u00a0\u00a0 192.168.56.30\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 N<\/code>\/A<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
Allowed node host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36 192.168.56.37 192.168.56.30<\/code><\/div>\n
Membership coordinator: 192.168.56.30<\/code><\/div>\n
Standby priority host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.37<\/code><\/div>\n
Promote Status:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>DB Type\u00a0\u00a0\u00a0\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/430001A8<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/430001A8<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby database(s) <\/code>in<\/code> sync<\/code> with master. It is safe to promote.<\/code><\/div>\n
[root@pgservertools efm-3.0]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Now that everything is ok, let\u2019s do a switchover<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># \/usr\/edb\/efm-3.0\/bin\/efm promote efm -switchover<\/code><\/div>\n
Promote<\/code>\/switchover<\/code> command<\/code> accepted by <\/code>local<\/code> agent. Proceeding with promotion and will reconfigure original master. Run the <\/code>'cluster-status'<\/code> command<\/code> for<\/code> information about the new cluster state.<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And if we run the cluster-status command during the switchover<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># \/usr\/edb\/efm-3.0\/bin\/efm cluster-status efm<\/code><\/div>\n
Cluster Status: efm<\/code><\/div>\n
VIP:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Agent Type\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Agent\u00a0 DB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Witness\u00a0\u00a0\u00a0\u00a0 192.168.56.30\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 N<\/code>\/A<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Idle\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UNKNOWN<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
Allowed node host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36 192.168.56.37 192.168.56.30<\/code><\/div>\n
Membership coordinator: 192.168.56.30<\/code><\/div>\n
Standby priority host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.37<\/code><\/div>\n
Promote Status:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>DB Type\u00a0\u00a0\u00a0\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/44000098<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>No master database was found.<\/code><\/div>\n
Idle Node Status (idle nodes ignored <\/code>in<\/code> XLog location comparisons):<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UNKNOWN\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Connection to 192.168.56.36:5436 refused. Check that the <\/code>hostname<\/code> and port are correct and that the postmaster is accepting TCP<\/code>\/IP<\/code> connections.<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And we can see the promoting phase<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># \/usr\/edb\/efm-3.0\/bin\/efm cluster-status efm<\/code><\/div>\n
Cluster Status: efm<\/code><\/div>\n
VIP:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Agent Type\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Agent\u00a0 DB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Witness\u00a0\u00a0\u00a0\u00a0 192.168.56.30\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 N<\/code>\/A<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Idle\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UNKNOWN<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Promoting\u00a0\u00a0 192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
Allowed node host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36 192.168.56.37 192.168.56.30<\/code><\/div>\n
Membership coordinator: 192.168.56.30<\/code><\/div>\n
Standby priority host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>(List is empty.)<\/code><\/div>\n
Promote Status:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>DB Type\u00a0\u00a0\u00a0\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/44000170<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>No standby databases were found.<\/code><\/div>\n
Idle Node Status (idle nodes ignored <\/code>in<\/code> XLog location comparisons):<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UNKNOWN\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Connection to 192.168.56.36:5436 refused. Check that the <\/code>hostname<\/code> and port are correct and that the postmaster is accepting TCP<\/code>\/IP<\/code> connections.<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And after a few time we can see that the new master is on pgserver2<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># \/usr\/edb\/efm-3.0\/bin\/efm cluster-status efm<\/code><\/div>\n
Cluster Status: efm<\/code><\/div>\n
VIP:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Agent Type\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Agent\u00a0 DB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Witness\u00a0\u00a0\u00a0\u00a0 192.168.56.30\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 N<\/code>\/A<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
Allowed node host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36 192.168.56.37 192.168.56.30<\/code><\/div>\n
Membership coordinator: 192.168.56.30<\/code><\/div>\n
Standby priority host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36<\/code><\/div>\n
Promote Status:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>DB Type\u00a0\u00a0\u00a0\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/440001A8<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/440001A8<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby database(s) <\/code>in<\/code> sync<\/code> with master. It is safe to promote.<\/code><\/div>\n
[root@pgservertools efm-3.0]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

The purpose of the witness is to do an automatic failover when the primary is down. Let\u2019s simulate a crash of our primary database by killing the corresponding process.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n<\/td>\n
\n
\n
[root@pgserver2 tmp]<\/code># ps -ef | grep postgres<\/code><\/div>\n
...<\/code><\/div>\n
...<\/code><\/div>\n
root\u00a0\u00a0\u00a0\u00a0 17529 14103\u00a0 0 16:45 pts<\/code>\/1<\/code>\u00a0\u00a0\u00a0 00:00:00 <\/code>tail<\/code> -f <\/code>\/u90\/mydata\/101\/log\/postgresql-2018-03-06<\/code>.log<\/code><\/div>\n
<strong>postgres 20612\u00a0\u00a0\u00a0\u00a0 1\u00a0 0 17:56 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 00:00:00 <\/code>\/u01\/app\/postgres\/product\/10\/db_1\/bin\/postgres<\/code> -D <\/code>\/u90\/mydata\/101<\/code><<\/code>\/strong<\/code>><\/code><\/div>\n
postgres 20613 20612\u00a0 0 17:56 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 00:00:00 postgres: logger process<\/code><\/div>\n
postgres 20615 20612\u00a0 0 17:56 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 00:00:00 postgres: checkpointer process<\/code><\/div>\n
postgres 20616 20612\u00a0 0 17:56 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 00:00:00 postgres: writer process<\/code><\/div>\n
postgres 20617 20612\u00a0 0 17:56 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 00:00:00 postgres: stats collector process<\/code><\/div>\n
postgres 20819 20612\u00a0 0 18:00 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 00:00:00 postgres: wal writer process<\/code><\/div>\n
postgres 20820 20612\u00a0 0 18:00 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 00:00:00 postgres: autovacuum launcher process<\/code><\/div>\n
postgres 20821 20612\u00a0 0 18:00 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 00:00:00 postgres: archiver process\u00a0\u00a0 last was 00000008.<\/code>history<\/code><\/div>\n
postgres 20822 20612\u00a0 0 18:00 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 00:00:00 postgres: bgworker: logical replication launcher<\/code><\/div>\n
postgres 20832 20612\u00a0 0 18:00 ?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 00:00:00 postgres: wal sender process repliuser 192.168.56.36(45827) streaming 0<\/code>\/440001A8<\/code><\/div>\n
root\u00a0\u00a0\u00a0\u00a0 21481 16868\u00a0 0 18:16 pts<\/code>\/0<\/code>\u00a0\u00a0\u00a0 00:00:00 <\/code>grep<\/code> --color=auto postgres<\/code><\/div>\n
[root@pgserver2 tmp]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And let\u2019s execute the kill command<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n<\/td>\n
\n
\n
[root@pgserver2 tmp]<\/code># kill -9 20612<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

If we check the cluster status from the witness server, we can see that the master is in an UNKNOWN status<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># \/usr\/edb\/efm-3.0\/bin\/efm cluster-status efm<\/code><\/div>\n
Cluster Status: efm<\/code><\/div>\n
VIP:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Agent Type\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Agent\u00a0 DB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Witness\u00a0\u00a0\u00a0\u00a0 192.168.56.30\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 N<\/code>\/A<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Idle\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UNKNOWN<\/code><\/div>\n
Allowed node host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36 192.168.56.37 192.168.56.30<\/code><\/div>\n
Membership coordinator: 192.168.56.30<\/code><\/div>\n
Standby priority host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36<\/code><\/div>\n
Promote Status:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>DB Type\u00a0\u00a0\u00a0\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Standby\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/440001A8<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>No master database was found.<\/code><\/div>\n
Idle Node Status (idle nodes ignored <\/code>in<\/code> XLog location comparisons):<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UNKNOWN\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Connection to 192.168.56.37:5436 refused. Check that the <\/code>hostname<\/code> and port are correct and that the postmaster is accepting TCP<\/code>\/IP<\/code> connections.<\/code><\/div>\n
[root@pgservertools efm-3.0]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

In the alert log in our standby server pgserver1, we can see that that the database is converted to a primary one a few time after.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n
28<\/div>\n
29<\/div>\n
30<\/div>\n
31<\/div>\n<\/td>\n
\n
\n
2018-03-06 18:17:49.381 CET [18384] FATAL:\u00a0 could not receive data from WAL stream: server closed the connection unexpectedly<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>This probably means the server terminated abnormally<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>before or <\/code>while<\/code> processing the request.<\/code><\/div>\n
2018-03-06 18:17:49.382 CET [18380] LOG:\u00a0 invalid record length at 0<\/code>\/440001A8<\/code>: wanted 24, got 0<\/code><\/div>\n
2018-03-06 18:17:49.387 CET [19049] FATAL:\u00a0 could not connect to the primary server: could not connect to server: Connection refused<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Is the server running on host <\/code>\"192.168.56.37\"<\/code> and accepting<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TCP<\/code>\/IP<\/code> connections on port 5436?<\/code><\/div>\n
2018-03-06 18:17:54.404 CET [19055] FATAL:\u00a0 could not connect to the primary server: could not connect to server: Connection refused<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Is the server running on host <\/code>\"192.168.56.37\"<\/code> and accepting<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TCP<\/code>\/IP<\/code> connections on port 5436?<\/code><\/div>\n
2018-03-06 18:17:59.406 CET [19107] FATAL:\u00a0 could not connect to the primary server: could not connect to server: Connection refused<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Is the server running on host <\/code>\"192.168.56.37\"<\/code> and accepting<\/code><\/div>\n
\u2026<\/code><\/div>\n
\u2026.<\/code><\/div>\n
\u2026.<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TCP<\/code>\/IP<\/code> connections on port 5436?<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TCP<\/code>\/IP<\/code> connections on port 5436?<\/code><\/div>\n
2018-03-06 18:18:34.450 CET [19128] FATAL:\u00a0 could not connect to the primary server: could not connect to server: Connection refused<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Is the server running on host <\/code>\"192.168.56.37\"<\/code> and accepting<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TCP<\/code>\/IP<\/code> connections on port 5436?<\/code><\/div>\n
2018-03-06 18:18:39.451 CET [19134] FATAL:\u00a0 could not connect to the primary server: could not connect to server: Connection refused<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Is the server running on host <\/code>\"192.168.56.37\"<\/code> and accepting<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TCP<\/code>\/IP<\/code> connections on port 5436?<\/code><\/div>\n
2018-03-06 18:18:44.462 CET [19135] FATAL:\u00a0 could not connect to the primary server: could not connect to server: Connection refused<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Is the server running on host <\/code>\"192.168.56.37\"<\/code> and accepting<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>TCP<\/code>\/IP<\/code> connections on port 5436?<\/code><\/div>\n
2018-03-06 18:18:49.456 CET [18380] LOG:\u00a0 trigger <\/code>file<\/code> found: <\/code>\/tmp\/postgresql<\/code>.trigger<\/code><\/div>\n
2018-03-06 18:18:49.456 CET [18380] LOG:\u00a0 redo <\/code>done<\/code> at 0<\/code>\/44000170<\/code><\/div>\n
2018-03-06 18:18:49.479 CET [18380] LOG:\u00a0 selected new timeline ID: 9<\/code><\/div>\n
2018-03-06 18:18:50.128 CET [18380] LOG:\u00a0 archive recovery complete<\/code><\/div>\n
2018-03-06 18:18:50.229 CET [18378] LOG:\u00a0 database system is ready to accept connections<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

What we can confirm by querying the cluster status<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># \/usr\/edb\/efm-3.0\/bin\/efm cluster-status efm<\/code><\/div>\n
Cluster Status: efm<\/code><\/div>\n
VIP:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Agent Type\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Agent\u00a0 DB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Witness\u00a0\u00a0\u00a0\u00a0 192.168.56.30\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 N<\/code>\/A<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Idle\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UNKNOWN<\/code><\/div>\n
Allowed node host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36 192.168.56.37 192.168.56.30<\/code><\/div>\n
Membership coordinator: 192.168.56.30<\/code><\/div>\n
Standby priority host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>(List is empty.)<\/code><\/div>\n
Promote Status:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>DB Type\u00a0\u00a0\u00a0\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/440002B8<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>No standby databases were found.<\/code><\/div>\n
Idle Node Status (idle nodes ignored <\/code>in<\/code> XLog location comparisons):<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.37\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UNKNOWN\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Connection to 192.168.56.37:5436 refused. Check that the <\/code>hostname<\/code> and port are correct and that the postmaster is accepting TCP<\/code>\/IP<\/code> connections.<\/code><\/div>\n
[root@pgservertools efm-3.0]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

and<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n<\/td>\n
\n
\n
[root@pgservertools efm-3.0]<\/code># \/usr\/edb\/efm-3.0\/bin\/efm cluster-status efm<\/code><\/div>\n
Cluster Status: efm<\/code><\/div>\n
VIP:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Agent Type\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Agent\u00a0 DB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Witness\u00a0\u00a0\u00a0\u00a0 192.168.56.30\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 N<\/code>\/A<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UP\u00a0\u00a0\u00a0\u00a0 UP<\/code><\/div>\n
Allowed node host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>192.168.56.36 192.168.56.37 192.168.56.30<\/code><\/div>\n
Membership coordinator: 192.168.56.30<\/code><\/div>\n
Standby priority host list:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>(List is empty.)<\/code><\/div>\n
Promote Status:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>DB Type\u00a0\u00a0\u00a0\u00a0 Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 XLog Loc\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Info<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>--------------------------------------------------------------<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>Master\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.56.36\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/code>\/440002B8<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>No standby databases were found.<\/code><\/div>\n
[root@pgservertools efm-3.0]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

On the old primary pgserver2 we can see the contents of the file recovery.conf automatically created by EDB Failover manager<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n<\/td>\n
\n
\n
[postgres@pgserver2 101]$ <\/code>cat<\/code> recovery.conf<\/code><\/div>\n
# EDB Failover Manager<\/code><\/div>\n
# This generated recovery.conf file prevents the db server from accidentally<\/code><\/div>\n
# being restarted as a master since a failover or promotion has occurred<\/code><\/div>\n
standby_mode = on<\/code><\/div>\n
restore_command = <\/code>'echo 2>\"recovery suspended on failed server node\"; exit 1'<\/code><\/div>\n
[postgres@pgserver2 101]$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

To rebuild our standby database we have to edit the recovery.conf file
\nConclusion<\/strong>
\nWe have seen in this blog how to configure edb-efm30. Note that a virtual IP can be also configured. The official documentation can help.<\/p>\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw Edb Failover Manager edb-efm30 is now released and supports PostgreSQL 10.1. Efm is an EDB tool which can be used to perform a switchover and a failover in a PostgreSQL standby environment. In this blog we are going to see how we can install and configure efm in a standby environment. We […]<\/p>\n","protected":false},"author":27,"featured_media":11007,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[1311,1312,1313,1314,857],"type_dbi":[],"class_list":["post-11006","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","tag-efm","tag-enterprisedb-efm","tag-failover-manager","tag-postgresql-10-1","tag-switchover"],"acf":[],"yoast_head":"\nEDB Failover Manager 3.0 and PostgreSQL 10.1 - dbi Blog<\/title>\n<meta name=\"description\" content=\"efm, enterprisedb efm, failover manager, postgresql 10.1,switchover\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"EDB Failover Manager 3.0 and PostgreSQL 10.1\" \/>\n<meta property=\"og:description\" content=\"efm, enterprisedb efm, failover manager, postgresql 10.1,switchover\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-03-07T15:31:27+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-09T14:54:26+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/config.png\" \/>\n\t<meta property=\"og:image:width\" content=\"834\" \/>\n\t<meta property=\"og:image:height\" content=\"581\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"EDB Failover Manager 3.0 and PostgreSQL 10.1\",\"datePublished\":\"2018-03-07T15:31:27+00:00\",\"dateModified\":\"2023-06-09T14:54:26+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/\"},\"wordCount\":583,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/config.png\",\"keywords\":[\"efm\",\"enterprisedb efm\",\"failover manager\",\"postgresql 10.1\",\"switchover\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/\",\"name\":\"EDB Failover Manager 3.0 and PostgreSQL 10.1 - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/config.png\",\"datePublished\":\"2018-03-07T15:31:27+00:00\",\"dateModified\":\"2023-06-09T14:54:26+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"efm, enterprisedb efm, failover manager, postgresql 10.1,switchover\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/config.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/config.png\",\"width\":834,\"height\":581},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/edb-failover-manager-3-0-and-postgresql-10-1\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"EDB Failover Manager 3.0 and PostgreSQL 10.1\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/oracle-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"EDB Failover Manager 3.0 and PostgreSQL 10.1 - dbi Blog","description":"efm, enterprisedb efm, failover manager, postgresql 10.1,switchover","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/","og_locale":"en_US","og_type":"article","og_title":"EDB Failover Manager 3.0 and PostgreSQL 10.1","og_description":"efm, enterprisedb efm, failover manager, postgresql 10.1,switchover","og_url":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/","og_site_name":"dbi Blog","article_published_time":"2018-03-07T15:31:27+00:00","article_modified_time":"2023-06-09T14:54:26+00:00","og_image":[{"width":834,"height":581,"url":"http:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/config.png","type":"image\/png"}],"author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"EDB Failover Manager 3.0 and PostgreSQL 10.1","datePublished":"2018-03-07T15:31:27+00:00","dateModified":"2023-06-09T14:54:26+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/"},"wordCount":583,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/config.png","keywords":["efm","enterprisedb efm","failover manager","postgresql 10.1","switchover"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/","url":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/","name":"EDB Failover Manager 3.0 and PostgreSQL 10.1 - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/config.png","datePublished":"2018-03-07T15:31:27+00:00","dateModified":"2023-06-09T14:54:26+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"efm, enterprisedb efm, failover manager, postgresql 10.1,switchover","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/config.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/config.png","width":834,"height":581},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/edb-failover-manager-3-0-and-postgresql-10-1\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"EDB Failover Manager 3.0 and PostgreSQL 10.1"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11006","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=11006"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11006\/revisions"}],"predecessor-version":[{"id":25764,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11006\/revisions\/25764"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/11007"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=11006"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=11006"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=11006"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=11006"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}