pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Lee Wu <Lwu@mxlogic.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: PG shutdown itself?
Date: Fri, 04 Mar 2005 11:50:34 -0600
Message-ID: <1109958634.30529.426.camel@state.g2switchworks.com> (raw)
In-Reply-To: <ECAB83AA52BCC043A0E24BBC000010241115A8@mxhq-exch.corp.mxlogic.com>
References: <ECAB83AA52BCC043A0E24BBC000010241115A8@mxhq-exch.corp.mxlogic.com>

On Fri, 2005-03-04 at 11:38, Lee Wu wrote:
> Greetings,
> 
>  
> 
> To best of my knowledge, nobody issued pg_ctl stop –m fast while 
> 
> we experienced PG was trying to shutdown unsuccessfully:
> 
>  
> 
> *** Everything seems normal before this point ***
> 
> Mar  3 21:07:55 myhost postgres[630]: [24] LOG:  recycled transaction
> log file 00001ABC0000006D
> 
> Mar  3 21:08:57 myhost postgres[5158]: [1] LOG:  fast shutdown request
> 
> Mar  3 21:08:57 myhost postgres[5158]: [2] LOG:  aborting any active
> transactions
> 
> Mar  3 21:08:57 myhost postgres[14292]: [1] FATAL:  This connection
> has been terminated by the administrator.
> 
> *** A lot of “This connection has been terminated by the
> administrator.” taken out here ***
> 
> Mar  3 21:08:57 myhost postgres[15912]: [3] FATAL:  The database
> system is shutting down
> 
> *** A lot the same message as last line till  ***
> 
> Mar  3 22:10:39 myhost postgres[1840]: [3] FATAL:  The database system
> is shutting down
> 
>  
> 
> Then I used “–m immediate”:
> 
> Mar  3 22:10:39 myhost postgres[5158]: [3] LOG:  immediate shutdown
> request
> 
> Mar  3 22:11:07 myhost postgres[1918]: [1] LOG:  database system was
> interrupted at 2005-03-03 21:08:53 MST
> 
> Mar  3 22:11:07 myhost postgres[1918]: [2] LOG:  checkpoint record is
> at 1ABC/929DFCB4
> 
> Mar  3 22:11:07 myhost postgres[1918]: [3] LOG:  redo record is at
> 1ABC/9044F3B4; undo record is at 0/0; shutdown FALSE
> 
> Mar  3 22:11:07 myhost postgres[1918]: [4] LOG:  next transaction id:
> 1090597972; next oid: 4231750970
> 
> Mar  3 22:11:07 myhost postgres[1918]: [5] LOG:  database system was
> not properly shut down; automatic recovery in progress
> 
> Mar  3 22:11:07 myhost postgres[1918]: [6] LOG:  redo starts at
> 1ABC/9044F3B4
> 
> Mar  3 22:11:07 myhost postgres[1919]: [1] FATAL:  The database system
> is starting up
> 
> *** PG was up after a lot of the above message ***
> 
>  
> 
> PG version is 7.3.2 on Red Hat Enterprise Linux ES release 3 (Taroon
> Update 4) 
> 
> I know it is old, but anyone can smell why PG shutdown itself?

This sounds like postgresql ran up against the Out Of Memory killer in
the linux kernel, but I thought it killed things with -9, which would
result in an immediate shutdown.  Maybe a ulimit issue?  Those are the
two most common causes of postgresql premature shutdown.



view thread (7+ messages)  latest in thread

Message-ID: <1109958634.30529.426.camel@state.g2switchworks.com>
Permalink:  ../1109958634.30529.426.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1109958634.30529.426.camel@state.g2switchworks.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: smarlowe@g2switchworks.com, Lwu@mxlogic.com
  Subject: Re: PG shutdown itself?
  In-Reply-To: <1109958634.30529.426.camel@state.g2switchworks.com>
  References: <ECAB83AA52BCC043A0E24BBC000010241115A8@mxhq-exch.corp.mxlogic.com> <1109958634.30529.426.camel@state.g2switchworks.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