pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Samuel Stearns <SStearns@internode.com.au>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Postgres Crash
Date: Thu, 09 Dec 2010 22:25:03 -0500
Message-ID: <12695.1291951503@sss.pgh.pa.us> (raw)
In-Reply-To: <68B59BEDCD36854AADBDF17E91B2937A07844CD029@EXCHMAIL.staff.internode.com.au>
References: <68B59BEDCD36854AADBDF17E91B2937A07844CD029@EXCHMAIL.staff.internode.com.au>

Samuel Stearns <SStearns@internode.com.au> writes:
> Environment:

> Solaris 10
> Postgres 8.3.12

> Postgres crashed and left 26 postmaster processes active in it's wake.  Killed the children and re-started postgres successfully.  Messages from the log:

> Dec 10 11:52:15 udrv postgres[771]: [ID 748848 local0.info] [6-1] host=,user=,db= LOG:  setsockopt(TCP_NODELAY) failed: Invalid argument
> Dec 10 11:52:20 udrv postgres[2183]: [ID 748848 local0.error] [1-1] host=,user=,db= FATAL:  pre-existing shared memory block (key 5432001, ID 0) is still in use
> Dec 10 11:52:20 udrv postgres[2183]: [ID 748848 local0.error] [1-2] host=,user=,db= HINT:  If you're sure there are no old server processes still running, remove the shared memory block with the
> Dec 10 11:52:20 udrv postgres[2183]: [ID 748848 local0.error] [1-3]  command "ipcclean", "ipcrm", or just delete the file "postmaster.pid".

> With the 'FATAL' and 'HINT' lines repeating.

> Any ideas what occurred here?

Nope.  The log entries above are from the restart attempt, and give no
information about the crash.  If you have any log entries from before
that, or have a core file that would yield a backtrace, maybe we could
draw some conclusions from that info.

			regards, tom lane



view thread (22+ messages)  latest in thread

Message-ID: <12695.1291951503@sss.pgh.pa.us>
Permalink:  ../12695.1291951503@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12695.1291951503@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, SStearns@internode.com.au
  Subject: Re: Postgres Crash
  In-Reply-To: <12695.1291951503@sss.pgh.pa.us>

* 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