MIME-Version: 1.0
From: nikhil Kumar <nikhil.psql123@gmail.com>
Date: Mon, 26 Jan 2026 20:48:22 +0530
Message-ID: 
 <CAEXynSs4VZoZhTFTzyvVXBNKGDrUVtvwiYWurN+6XPTV3HfGEg@mail.gmail.com>
Subject: EFM -switchover error
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000034400006494c05e5"
Archived-At: 
 <https://www.postgresql.org/message-id/CAEXynSs4VZoZhTFTzyvVXBNKGDrUVtvwiYWurN%2B6XPTV3HfGEg%40mail.gmail.com>
Precedence: bulk

--00000000000034400006494c05e5
Content-Type: text/plain; charset="UTF-8"

Dear Team,

I have configured the EFM with the edb-15 environment. initially primary
and secondary are in sync. But once the switchover happen timeline is
changing and getting the below error. Please give a permanent solution


Before switchover:

[image: image.png]

After switchover.
[image: image.png]

error log :  [enterprisedb@localhost ~]$ cd /var/log/efm-5.2/
[enterprisedb@localhost efm-5.2]$ ll
total 192
-rw-r--r--. 1 efm efm 196487 Jan 26 20:12 efm.log
[enterprisedb@localhost efm-5.2]$ tail -10 efm.log
Error: com.sun.mail.util.MailConnectException: Couldn't connect to host,
port: localhost, 25; timeout 60000;
  nested exception is:
        java.net.ConnectException: Connection refused.
2026-01-26 20:12:31 com.enterprisedb.efm.DBMonitor lambda$watchDB$1 WARN:
Database connection is null.
2026-01-26 20:12:34 com.enterprisedb.efm.admin.AdminServerThread
processRequest INFO: Admin server received status request.
2026-01-26 20:12:34 com.enterprisedb.efm.admin.AdminServerThread
processRequest INFO: Received param: efm
2026-01-26 20:12:34 com.enterprisedb.efm.nodes.EfmNode checkClusterStatus
INFO: Sending status message to all nodes: node_status
2026-01-26 20:12:34 com.enterprisedb.efm.nodes.EfmAgent handleStatusCall
INFO: responding to db status request with status:
Standby%%192.168.75.142%%true%%192.168.75.150%%false
2026-01-26 20:12:34 com.enterprisedb.efm.nodes.EfmNode checkClusterStatus
INFO: Status response: EfmStatus{nodeStatusList=[NodeStatus{type='Witness',
address=localhost-17356(192.168.75.149)}, NodeStatus{type='Standby',
address=localhost-64370(192.168.75.142)}, NodeStatus{type='Primary',
address=localhost-39617(192.168.75.148)}]}
2026-01-26 20:12:34 com.enterprisedb.efm.nodes.EfmNode checkClusterStatus
INFO: Current internal status: [ total nodes: 3 primary:
localhost-39617(192.168.75.148) promoting: null standbys (1):
localhost-64370(192.168.75.142)  witnesses (1):
localhost-17356(192.168.75.149)  idle nodes (0):  failed (0):  ]

--00000000000034400006494c05e5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear Team,<div><br></div><div>I have configured the EFM wi=
th the edb-15 environment. initially primary and secondary=C2=A0are in sync=
. But once the switchover happen timeline is changing=C2=A0and getting=C2=
=A0the below error. Please give a=C2=A0permanent=C2=A0solution<br><br><br><=
/div><div>Before switchover:</div><div><br></div><div><img src=3D"cid:ii_mk=
vaals61" alt=3D"image.png" width=3D"452" height=3D"258"><br></div><div><br>=
</div><div>After switchover.</div><div><img src=3D"cid:ii_mkva9azj0" alt=3D=
"image.png" width=3D"452" height=3D"145"></div><div><br></div><div>error lo=
g :=C2=A0 [enterprisedb@localhost ~]$ cd /var/log/efm-5.2/</div>[enterprise=
db@localhost efm-5.2]$ ll<br>total 192<br>-rw-r--r--. 1 efm efm 196487 Jan =
26 20:12 efm.log<br>[enterprisedb@localhost efm-5.2]$ tail -10 efm.log<br>E=
rror: com.sun.mail.util.MailConnectException: Couldn&#39;t connect to host,=
 port: localhost, 25; timeout 60000;<br>=C2=A0 nested exception is:<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 java.net.ConnectException: Connection refused.<br>=
2026-01-26 20:12:31 com.enterprisedb.efm.DBMonitor lambda$watchDB$1 WARN: D=
atabase connection is null.<br>2026-01-26 20:12:34 com.enterprisedb.efm.adm=
in.AdminServerThread processRequest INFO: Admin server received status requ=
est.<br>2026-01-26 20:12:34 com.enterprisedb.efm.admin.AdminServerThread pr=
ocessRequest INFO: Received param: efm<br>2026-01-26 20:12:34 com.enterpris=
edb.efm.nodes.EfmNode checkClusterStatus INFO: Sending status message to al=
l nodes: node_status<br>2026-01-26 20:12:34 com.enterprisedb.efm.nodes.EfmA=
gent handleStatusCall INFO: responding to db status request with status: St=
andby%%192.168.75.142%%true%%192.168.75.150%%false<br>2026-01-26 20:12:34 c=
om.enterprisedb.efm.nodes.EfmNode checkClusterStatus INFO: Status response:=
 EfmStatus{nodeStatusList=3D[NodeStatus{type=3D&#39;Witness&#39;, address=
=3Dlocalhost-17356(192.168.75.149)}, NodeStatus{type=3D&#39;Standby&#39;, a=
ddress=3Dlocalhost-64370(192.168.75.142)}, NodeStatus{type=3D&#39;Primary&#=
39;, address=3Dlocalhost-39617(192.168.75.148)}]}<br>2026-01-26 20:12:34 co=
m.enterprisedb.efm.nodes.EfmNode checkClusterStatus INFO: Current internal =
status: [ total nodes: 3 primary: localhost-39617(192.168.75.148) promoting=
: null standbys (1): localhost-64370(192.168.75.142) =C2=A0witnesses (1): l=
ocalhost-17356(192.168.75.149) =C2=A0idle nodes (0): =C2=A0failed (0): =C2=
=A0]<br></div>

--00000000000034400006494c05e5--