pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: John R Allgood <jallgood@the-allgoods.net>
Cc: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: How to monitor resources on Linux.
Date: Tue, 28 Aug 2007 16:06:26 -0500
Message-ID: <dcc563d10708281406r18c8447fkf354e0d696e4374d@mail.gmail.com> (raw)
In-Reply-To: <46D489B6.8050804@the-allgoods.net>
References: <46D4353F.2040209@the-allgoods.net>
	<815.1188324416@sss.pgh.pa.us>
	<46D470D8.2030605@the-allgoods.net>
	<20070828191143.GE13868@alvh.no-ip.org>
	<46D47A13.3060907@the-allgoods.net>
	<20070828195554.GB1683@phlogiston.dyndns.org>
	<dcc563d10708281324i7aee72faj60d5e43aa52a2f1c@mail.gmail.com>
	<46D489B6.8050804@the-allgoods.net>

On 8/28/07, John R Allgood <jallgood@the-allgoods.net> wrote:
>
>  Here is the output from free on one of the nodes. I have seen free mem go
> as low as 15 and then go back up. Like I was saying earlier my concern was
> why the kernel started killing my postmasters. Here is the kernel message
> "kernel: oom-killer: gfp_mask=0xd0". This started happening when were
> running our midday backup. After backup runs vacuum will start up right
> after. We rebooted the servers last night and today backup and vacuum ran
> fine. Below the free out put I have added the logging out of
> /var/log/messages. Thanks this is a great list.
>
>  i                             total       used       free     shared
> buffers     cached
>  Mem:          8116       5969       2146          0        144       4318
>  Low:           821        510        310
>  High:         7294       5459       1835
>  -/+ buffers/cache:       1506       6609
>  Swap:         2000          0       1999

I'm assuming those numbers are in megabytes.  If so, then they're
pretty realistic.  you've 2 Gig free, and 4 Gig cached, with 144 Meg
buffer mem.  Very reasonable.  Have you got the output of free when
things are going wrong?

>  ug 27 12:24:42 gan-lxc-01 kernel: Swap cache: add 2104, delete 2017, find
> 829/1136, race 0+0
>  Aug 27 12:24:42 gan-lxc-01 kernel: 1229 bounce buffer pages
>  Aug 27 12:24:42 gan-lxc-01 kernel: Free swap:       2047424kB
>  Aug 27 12:24:42 gan-lxc-01 kernel: 2260992 pages of RAM
>  Aug 27 12:24:42 gan-lxc-01 kernel: 1867512 pages of HIGHMEM
>  Aug 27 12:24:42 gan-lxc-01 kernel: 183273 reserved pages
>  Aug 27 12:24:42 gan-lxc-01 kernel: 942026 pages shared
>  Aug 27 12:24:42 gan-lxc-01 kernel: 87 pages swap cached
>  Aug 27 12:24:42 gan-lxc-01 kernel: Out of Memory: Killed process 19383
> (postmaster).

IS there any other context to go with this, like something from the
postgres logs at the same time, maybe top output sorted by memory...

I'm wondering if you're just running a few queries that fire really
big sorts off and that's what's getting you.



view thread (28+ messages)  latest in thread

Message-ID: <dcc563d10708281406r18c8447fkf354e0d696e4374d@mail.gmail.com>
Permalink:  ../dcc563d10708281406r18c8447fkf354e0d696e4374d@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10708281406r18c8447fkf354e0d696e4374d@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: scott.marlowe@gmail.com, jallgood@the-allgoods.net, ajs@crankycanuck.ca
  Subject: Re: How to monitor resources on Linux.
  In-Reply-To: <dcc563d10708281406r18c8447fkf354e0d696e4374d@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox