| From: | bricklen <bricklen(at)gmail(dot)com> |
|---|---|
| To: | Niels Kristian Schjødt <nielskristian(at)autouncle(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org list" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: URGENT issue: pg-xlog growing on master! |
| Date: | 2013-06-10 14:36:03 |
| Message-ID: | CAGrpgQ9mc+jwqj_ZK4MCFmx7RaSifdPDsCRaw0qT=bG0RTLMVg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Jun 10, 2013 at 4:29 AM, Niels Kristian Schjødt <
nielskristian(at)autouncle(dot)com> wrote:
>
> 2013-06-10 11:21:45 GMT FATAL: could not connect to the primary server:
> could not connect to server: No route to host
> Is the server running on host "192.168.0.4" and accepting
> TCP/IP connections on port 5432?
>
Did anything get changed on the standby or master around the time this
message started occurring?
On the master, what do the following show?
show port;
show listen_addresses;
The master's IP is still 192.168.0.4?
Have you tried connecting to the master using something like:
psql -h 192.168.0.4 -p 5432 -U postgres -d postgres
Does that throw a useful error or warning?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Niels Kristian Schjødt | 2013-06-10 15:35:41 | Re: URGENT issue: pg-xlog growing on master! |
| Previous Message | Ghislain ROUVIGNAC | 2013-06-10 13:58:55 | Re: Not same plan between static and prepared query |