pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Jeremy Ashcraft <jashcraft@edgate.com>
To: pgsql-admin@postgresql.org
Subject: Re: strange hung processes
Date: Thu, 02 Feb 2006 09:32:08 -0800
Message-ID: <43E24218.3030803@edgate.com> (raw )
In-Reply-To: <43E23D4B.7060101@edgate.com >
References: <43E23D4B.7060101@edgate.com >
I forgot to include the process list:
postgres 13214 5142 0 Jan09 ? 00:00:00 postgres: postgre edgate
10.1.1.3 authentication
postgres 13215 5142 0 Jan09 ? 00:00:00 postgres: postgre edgate
10.1.1.1 authentication
postgres 13216 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
postgres 13217 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13218 5142 0 Jan09 ? 00:00:00 postgres: postgre edgate
10.1.1.1 authentication
postgres 13219 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13220 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13221 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13222 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
postgres 13223 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13224 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
postgres 13225 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
postgres 13226 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13227 5142 0 Jan09 ? 00:00:00 postgres: snuser
sn_master 10.1.1.3 authentication
postgres 13228 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
postgres 13229 5142 0 Jan09 ? 00:00:00 postgres: postgre
sn_master 10.1.1.3 authentication
Jeremy Ashcraft wrote:
> We're running 7.4.9 and have run into something strange.
> A group of processes seem to have hung and cannot be killed. netstat
> showed that there were no active TCP connections at the time. Sending
> SIGTERM to the parent process caused PG to begin its shutdown, but it
> never finished. We then kill -9 the postmaster, which caused it to
> die, but these child procs remain, even after a clean restart. Our
> next step is to reboot the box, but before we do, I'm just curious
> anyone else has seen this, why this happened, and if anyone know ways
> to prevent this from happening again.....
>
> thanks
>
--
jeremy ashcraft
operations/development
EDucation GATEways
jashcraft@edgate.com
view thread (6+ messages) latest in thread
Message-ID: <43E24218.3030803@edgate.com>
Permalink: ../43E24218.3030803@edgate.com/
Also on: postgresql.org/message-id/43E24218.3030803@edgate.com
copy link · copy postgr.es
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: jashcraft@edgate.com
Subject: Re: strange hung processes
In-Reply-To: <43E24218.3030803@edgate.com>
References: <43E23D4B.7060101@edgate.com> <43E24218.3030803@edgate.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