| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Burgholzer, Robert (DEQ)" <Robert(dot)Burgholzer(at)deq(dot)virginia(dot)gov> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: diagnosing a db crash - server exit code 2 |
| Date: | 2011-09-23 19:42:54 |
| Message-ID: | CAOR=d=3BoU+CRsOLVWY7a870cdQ2uc9KQcBA43cT-5J1_CKhow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, Sep 23, 2011 at 1:38 PM, Burgholzer, Robert (DEQ)
<Robert(dot)Burgholzer(at)deq(dot)virginia(dot)gov> wrote:
> Joe,
> Thanks - I will try to check into this - however, we have done some tuning
> on the memory over the last 2 years and gotten it such that it is seldom if
> every having to dip into its swap too substantially -- according to "top",
> we remain under 1% swap usage during most times. Generally speaking, I run
> 3-5 of these large PHP processes simultaneously with no issue, however, when
> I issue even a "median" function call, after several calls (no consistent
> pattern that I can discern), the backend crashes.
>
> If this were the OOM killer - any way I would diagnose it?
If it's the OOM killer it'll be in your /var/log/messages log.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2011-09-23 20:31:12 | Re: diagnosing a db crash - server exit code 2 |
| Previous Message | Burgholzer, Robert (DEQ) | 2011-09-23 19:38:19 | Re: diagnosing a db crash - server exit code 2 |