Re: diagnosing a db crash - server exit code 2
От | Robert Burgholzer |
---|---|
Тема | Re: diagnosing a db crash - server exit code 2 |
Дата | |
Msg-id | CACT-NGJNW92jOFfp9N4u9APrmV0WjnJwg1ix37-yESWWSCDO2g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: diagnosing a db crash - server exit code 2 ("Burgholzer, Robert (DEQ)" <Robert.Burgholzer@deq.virginia.gov>) |
Ответы |
Re: diagnosing a db crash - server exit code 2
(Joe Conway <mail@joeconway.com>)
|
Список | pgsql-admin |
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.
regards,
r.b.
--
--
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
On Mon, Oct 3, 2011 at 12:54 PM, Burgholzer, Robert (DEQ) <Robert.Burgholzer@deq.virginia.gov> wrote:
OK,
So I have upgraded to the latest plR, and restarted my PG backend and
reloaded my PG functions that call R/PlR. I am still able to make the
process crash by running my R functions. When trying to obtain the
stack trace, however, I notice that it appears as if the process that is
CAUSING the crash, is not SUFFERING the crash, as per this message while
executing the offending SQL/pLR. I have my PHP process running in the
background, making no R calls but involving heavy traffic on the PG
server, and I opened up a psql console and executed the troublesome
command (a large quantile call) - then I ran a trace on the psql console
session, and got the following at the PG command line while waiting for
the query to finish:
<psql>
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
</psql>
This is backed up by the debuglog.txt giving me no feedback:
<debuglog.txt>
Continuing.
Program exited normally.
</debuglog.txt>
Is it even possible that something like this is happening -- i.e.,
calling R from a different process kills another backend? How do I
figure out which process to watch?
Thanks,
r.b.
Robert W. Burgholzer
Surface Water Modeler
Office of Water Supply and Planning
Virginia Department of Environmental Quality
rwburgholzer@deq.virginia.gov
804-698-4405
Open Source Modeling Tools:
http://sourceforge.net/projects/npsource/
-----Original Message-----
From: Joe Conway [mailto:mail@joeconway.com]
Sent: Thursday, September 29, 2011 1:30 PM
To: Robert Burgholzer
Cc: Burgholzer, Robert (DEQ); Scott Marlowe; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] diagnosing a db crash - server exit code 2
On 09/28/2011 12:54 PM, Robert Burgholzer wrote:
> Just a quick checkin on this problem. Thus far, I have managed to
> install dbg and recompile postgresql with the appropriate debugging
> headers/variables.
I might have missed it, but are you already running the latest version
of PL/R (8.3.0.13)?
Joe
--
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
В списке pgsql-admin по дате отправления: