| From: | David Rees <drees76(at)gmail(dot)com> |
|---|---|
| To: | Tory M Blue <tmblue(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: oom_killer |
| Date: | 2011-04-22 18:15:57 |
| Message-ID: | BANLkTik6ah914Fbkf4sM1+V-z5c_2Ji2zw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Apr 21, 2011 at 1:28 AM, Tory M Blue <tmblue(at)gmail(dot)com> wrote:
> this is a Fedora 12 system, 2.6.32.23-170. I've been reading and
> appears this is yet another fedora bug, but so far I have not found
> any concrete evidence on how to fix it.
If it's a "fedora" bug, it's most likely related to the kernel where
the OOM-killer lives which really makes it more of a kernel bug than a
fedora bug as fedora kernels generally track upstream very closely.
Given that both the version of Fedora you're using is no longer
supported, at a minimum you should be running F-13 (or preferably F-14
since F-13 will lose maintenance in appx 2 months). If you have to
stay on F-12 you might at least try building the latest
2.6.32-longterm kernel which is up to version 2.6.32.39.
All that said - have you tried tracking memory usage of the machine
leading up to OOM killer events?
-Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tory M Blue | 2011-04-22 18:22:39 | Re: oom_killer |
| Previous Message | Tory M Blue | 2011-04-22 17:18:36 | Re: oom_killer |