Обсуждение: BUG #17063: repmgrd_upstream_reconnect getting more
The following bug has been logged on the website: Bug reference: 17063 Logged by: Mohan nagandlla Email address: nagandllamohan@gmail.com PostgreSQL version: 13.3 Operating system: Alpine Description: I have installed the repmgr for multi HA replication all are going good but in some times i am getting this logs how can we debug this bash-5.1$ repmgr cluster events Node ID | Name | Event | OK | Timestamp | Details ---------+----------+----------------------------+----+---------------------+----------------------------------------------------------------------------------------- 1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 07:22:28 | reconnected to upstream node after 0 seconds 1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 06:39:57 | reconnected to upstream node after 0 seconds 1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 06:28:33 | reconnected to upstream node after 0 seconds 1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 05:57:32 | reconnected to upstream node after 0 seconds 1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 05:35:56 | reconnected to upstream node after 0 seconds 1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 04:36:10 | reconnected to upstream node after 0 seconds 1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 04:26:18 | reconnected to upstream node after 0 seconds
Any update on this?
On Fri, 18 Jun 2021, 13:07 PG Bug reporting form, <noreply@postgresql.org> wrote:
The following bug has been logged on the website:
Bug reference: 17063
Logged by: Mohan nagandlla
Email address: nagandllamohan@gmail.com
PostgreSQL version: 13.3
Operating system: Alpine
Description:
I have installed the repmgr for multi HA replication all are going good but
in some times i am getting this logs how can we debug this
bash-5.1$ repmgr cluster events
Node ID | Name | Event | OK | Timestamp
| Details
---------+----------+----------------------------+----+---------------------+-----------------------------------------------------------------------------------------
1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 07:22:28
| reconnected to upstream node after 0 seconds
1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 06:39:57
| reconnected to upstream node after 0 seconds
1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 06:28:33
| reconnected to upstream node after 0 seconds
1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 05:57:32
| reconnected to upstream node after 0 seconds
1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 05:35:56
| reconnected to upstream node after 0 seconds
1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 04:36:10
| reconnected to upstream node after 0 seconds
1 | PG-Node1 | repmgrd_upstream_reconnect | t | 2021-06-18 04:26:18
| reconnected to upstream node after 0 seconds
> On 22 Jun 2021, at 13:07, Mohan Nagandlla <nagandllamohan@gmail.com> wrote: > > Any update on this? This bug reporting tool is for the core postgres server, contacting the repmgr developers is probably a better place to start to get help. -- Daniel Gustafsson https://vmware.com/