| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Dhruv Shukla <dhruvshukla82(at)gmail(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "jayknowsunix(at)gmail(dot)com" <jayknowsunix(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Problems with PG 9.3 |
| Date: | 2014-08-26 15:57:15 |
| Message-ID: | CAOR=d=1kJ8V29Nmqmso+3_HbdUAf-vV5fYAnNyYEkks1Y-1McA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Aug 26, 2014 at 9:27 AM, Dhruv Shukla <dhruvshukla82(at)gmail(dot)com> wrote:
> On viewing server logs on postgres server found the error as
> FATAL: connection to client lost
>
> There has been some improvements, like few of the getting stuck DB functions
> ran good. But the main ones are still failing.
This sounds like a firewall issue to me, but it could be a backend
running out of memory and the oom killer in linux killing it. I
believe oom killer logs to /var/log/syslog or /var/log/messages. Got
anything in those logs about that time for the oom killer?
If not, it could be a firewall, if you have one, between the app and
db boxes. If that's the case you can stop it from happening by
lowering the tcp keepalive settings.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2014-08-26 15:58:40 | Re: Problems with PG 9.3 |
| Previous Message | Dhruv Shukla | 2014-08-26 15:27:27 | Re: Problems with PG 9.3 |