X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 60DD49DC864 for ; Thu, 2 Feb 2006 13:32:21 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 17873-07 for ; Thu, 2 Feb 2006 13:32:19 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from bubka.webhack.com (bubka.webhack.com [64.34.168.26]) by postgresql.org (Postfix) with ESMTP id 1C31A9DC85E for ; Thu, 2 Feb 2006 13:32:16 -0400 (AST) Received: (qmail 15107 invoked by uid 89); 2 Feb 2006 17:32:16 -0000 Received: by simscan 1.1.0 ppid: 15098, pid: 15103, t: 1.4265s scanners: clamav: 0.87.1/m:34/d:1162 spam: 3.1.0 Received: from unknown (HELO ?192.168.0.237?) (ashcraft@13monkeys.com@64.91.109.105) by bubka.webhack.com with SMTP; 2 Feb 2006 17:32:15 -0000 Message-ID: <43E24218.3030803@edgate.com> Date: Thu, 02 Feb 2006 09:32:08 -0800 From: Jeremy Ashcraft User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: strange hung processes References: <43E23D4B.7060101@edgate.com> In-Reply-To: <43E23D4B.7060101@edgate.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.12 required=5 tests=[AWL=0.120] X-Spam-Score: 0.12 X-Spam-Level: X-Archive-Number: 200602/22 X-Sequence-Number: 20443 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