DBA Hub

📋Steps in this guide1/2

edb efm start failed with authentication failed error on standby - DBACLASS DBACLASS

edb efm start failed with authentication failed error on standby . Check the allow node list in primary and add the standby ip in allow node list.

postgresql configurationintermediate
by PostgreSQL
13 views
1

PROBLEM:

We have rebooted both the primary and standby postgres nodes. After the reboot , the enterprise failover manager(EFM) , was not getting started on the standby node. PRIMARY NODE – 10.20.30.40 STANDBY NODE – 10.20.30.41

Code/Command (click line numbers to comment):

1
2
3
4
5
6
7
8
9
10
11
12
[root@STANDBY efm-3.9]# <span style="color: #ff0000;"><strong>systemctl start edb-efm-3.9</strong></span>
Job for edb-efm-3.9.service failed because the control process exited with error code. See "systemctl status edb-efm-3.9.service" and "journalctl -xe" for details.

-- Check the log 
<span style="color: #ff0000;"><strong>cat /var/log/efm-3.9/efm.log
</strong></span>

        at com.enterprisedb.efm.nodes.EfmAgent.run(EfmAgent.java:211)
        at com.enterprisedb.efm.main.ServiceCommand.main(ServiceCommand.java:111)
2021-06-28 11:14:10 com.enterprisedb.efm.nodes.EfmAgent run ERROR: Exception starting service
<em><strong>java.lang.SecurityException: authentication failed
</strong></em>
2

SOLUTION:

Check the cluster status on primary node: Here, we don’t see the entry for standby server. So let’s add that in allow node list. Run allow-node on primary Start the efm service on standby server. It succeeded this time. Check the cluster status again. Cluster status:

Code/Command (click line numbers to comment):

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
[root@PRIMARY ~]# <span style="color: #ff0000;"><strong>/usr/edb/efm-3.9/bin/efm cluster-status efm</strong></span>
Cluster Status: efm

        Agent Type  Address              Agent  DB       VIP
        -----------------------------------------------------------------------
        Master      10.20.30.40         UP     UP

Allowed node host list:
        10.20.30.40

Membership coordinator: 10.20.30.40

Standby priority host list:
        (List is empty.)

Promote Status:

        DB Type     Address              WAL Received LSN   WAL Replayed LSN   Info
        ---------------------------------------------------------------------------
        Master      10.20.30.40                             3/80000D0

        No standby databases were found.

[root@PRIMARY ~]# <span style="color: #ff0000;"><strong>/usr/edb/efm-3.4/bin/efm allow-node  efm 10.20.30.41

</strong></span>

[root@STANDBY efm-3.9]# <span style="color: #ff0000;"><strong>systemctl start edb-efm-3.9
</strong></span>

[root@STANDBY ~]#  <span style="color: #ff0000;"><strong>/usr/edb/efm-3.9/bin/efm cluster-status efm</strong></span>
Cluster Status: efm

        Agent Type  Address              Agent  DB       VIP
        -----------------------------------------------------------------------
        Master      10.20.30.40          UP     UP
        Standby     10.20.30.41          UP     UP

Allowed node host list:
        10.20.30.40 10.20.30.41

Membership coordinator: 10.20.30.40

Standby priority host list:
        10.20.30.41

Promote Status:

        DB Type     Address              WAL Received LSN   WAL Replayed LSN   Info
        ---------------------------------------------------------------------------
        Master      10.20.30.40                             3/80001B0
        Standby     10.20.30.41          3/80001B0          3/80001B0

        Standby database(s) in sync with master. It is safe to promote.

Comments (0)

Please to add comments

No comments yet. Be the first to comment!