Skip site navigation (1) Skip section navigation (2)

Re: diagnosing a db crash - server exit code 2

From: Robert Burgholzer <rburghol(at)vt(dot)edu>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: "Burgholzer, Robert (DEQ)" <Robert(dot)Burgholzer(at)deq(dot)virginia(dot)gov>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: diagnosing a db crash - server exit code 2
Date: 2011-10-04 19:29:21
Message-ID: CACT-NGK7AVLydPGLbPufZVd8ef54sNpTsByVP_UV4aEnUCBs1A@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
OK,
So, now I am starting to think that I did something erroneous when
restarting the PG server, because after the most recent crash on my dev
server, it is now seemingly uncrashable.  Which makes me think it is FIXED
by the upgrade to 0.13 - which is awesome.  Though I was pretty certain that
I had restarted the PG process - but it is possible that I missed it of
course.

FWIW, I used the following command:
   pg_ctl -D /var/lib/pgsql/data restart -l logfile

I have run the test query 1,000 times in a loop on my dev server without a
crash now, and it managed to crash the live server in a test after about 20
invocations earlier today.

So, thanks to everyone, I will chalk this up as a great learning experience,
I have managed to get my stack traces and so forth, so that is awesome.
Your patience and willingness to help has been awesome.

r.b.

On Mon, Oct 3, 2011 at 1:28 PM, Joe Conway <mail(at)joeconway(dot)com> wrote:

> On 10/03/2011 10:10 AM, Robert Burgholzer wrote:
> > FWIW - I am currently trying this while tracing the process that I
> > assume is the postmaster (/usr/bin/postgres -D /home/postgres/data),
> > since this process number indicates that it was recently restarted -
> > although the other PG processes, writer, wal writer, autovacuum, stats
> > collector all have their older pids indicating that they still survive.
>
> Sounds like you are attaching to the wrong process. Try something like
> the below...
>
> Joe
>
>
>
> Session #1: (connect to db and load PL/R)
> -----------------
> #psql contrib_regression
> psql (9.2devel)
> Type "help" for help.
>
> contrib_regression=# load '$libdir/plr';
> LOAD
>
> Session #2: (use ps to find backend and attach)
> -----------------
> # ps -ef |grep postgres
> postgres 17001     1  0 Sep24 ?        00:00:16
> /usr/local/pgsql-head/bin/postgres -D /usr/local/pgsql-head/data -p 55437
> -i
> postgres 17006 17001 0 Sep24 ?        00:02:18 postgres: writer process
>
> postgres 17007 17001 0 Sep24 ?        00:01:50 postgres: wal writer
> process
> postgres 17008 17001 0 Sep24 ?        00:00:37 postgres: autovacuum
> launcher process
> postgres 17009 17001 0 Sep24 ?        00:00:47 postgres: stats
> collector process
> postgres 26631 17001  0 10:22 ?        00:00:00 postgres: postgres
> contrib_regression [local] idle
>
> #gdb /usr/local/pgsql-head/bin/postgres 26631
> (gdb) continue
> Continuing.
>
>
> Session #1: (run crashing function)
> -----------------
> run your PL/R function that causes the crash
>
>
> --
> Joe Conway
> credativ LLC: http://www.credativ.us
> Linux, PostgreSQL, and general Open Source
> Training, Service, Consulting, & 24x7 Support
>



-- 
--
Robert W. Burgholzer
http://www.findingfreestyle.com/
On Facebook -
http://www.facebook.com/pages/Finding-Freestyle/151918511505970
Twitter - http://www.twitter.com/findfreestyle
What's a tweeted swim set? A Sweet? No, a #swaiku!  Get them by following
http://twitter.com/findfreestyle

In response to

Responses

pgsql-admin by date

Next:From: Joe ConwayDate: 2011-10-04 19:41:38
Subject: Re: diagnosing a db crash - server exit code 2
Previous:From: Robert BurgholzerDate: 2011-10-04 19:18:08
Subject: Re: diagnosing a db crash - server exit code 2

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group