| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | vijay patil <vijay(dot)postgres(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Pgpool with high availability |
| Date: | 2024-05-29 14:14:49 |
| Message-ID: | e01753d9-cf6c-423a-a1c8-dfa6276ba846@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/28/24 22:15, vijay patil wrote:
> Hi Adrian,
>
> After modifying the pgpool.conf configuration to correct a subnet
> mistake, Previously, the wrong subnet was specified as /26, and it has
> now been corrected to /24. The configuration changes were as follows:
This seems to be a networking issue:
[root(at)staging-ha0001 ~]# ping 10.127.1.18
PING 10.127.1.18 (10.127.1.18) 56(84) bytes of data.
From 10.127.1.10 icmp_seq=1 Destination Host Unreachable
<...>
Where are ha0001 and ha0003 on the network relative to ha0002?
Also are they reachable for other services?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-05-29 15:10:27 | Re: Use of inefficient index in the presence of dead tuples |
| Previous Message | Greg Sabino Mullane | 2024-05-29 13:19:10 | Re: Timeout gets unset on a syntax error. |