Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 33E259FB975 for ; Mon, 21 May 2007 18:57:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 90191-10 for ; Mon, 21 May 2007 18:57:30 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.232]) by postgresql.org (Postfix) with ESMTP id 846DC9FB467 for ; Mon, 21 May 2007 18:57:30 -0300 (ADT) Received: by nz-out-0506.google.com with SMTP id s1so2392321nze for ; Mon, 21 May 2007 14:57:29 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=VfTCeBllC8e5T2UW3/2HvnmGLzDk2+J716XG7p1DC3SxLuhZJFnOYY2/dCWGqr6vwSvhrCTAyPSJHwT11g1sHTvDrpEuC/st1LPhpPZ7pV4cYKZ8pVtz8CKmug9axj2CpvSbKnuvk2ckzH4hseOrywLUM1vNGK8og4FMO9STo78= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=DF4+nsPRSNbrAHowyh84IWaN7d611Kv8VnnyLcydLEqyHZli1zlkj7NbnThwTKux3PEIWdNzB1iqKmEjRQFMhIs6u9Zt8MAD2v1bnJv2x+e6lxdcekVeSbJAcq0Tzw8XnqIHzP+DZ0DjKnsnnoYtGhG6q0yMfsDCUzEh+QNEB5w= Received: by 10.114.174.2 with SMTP id w2mr2931867wae.1179784648956; Mon, 21 May 2007 14:57:28 -0700 (PDT) Received: by 10.114.197.11 with HTTP; Mon, 21 May 2007 14:57:28 -0700 (PDT) Message-ID: <4544e0330705211457k30c0cd40oec47e830a0791a9d@mail.gmail.com> Date: Mon, 21 May 2007 16:57:28 -0500 From: "Peter Koczan" To: pgsql-admin Subject: trouble restarting a server MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_86943_6288173.1179784648903" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/213 X-Sequence-Number: 25533 ------=_Part_86943_6288173.1179784648903 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all, I'm having some trouble restarting a long-running server. Basically, pg_ctl can't kill any processes waiting on a notify interrupt. Here's what happened after trying a "stop -m fast" [root@vero ~]# ps axvw | grep post 3606 ? S 3:30 23 3260 41575 6644 0.1 /usr/bin/postgres -D /postgres/db-8.2 4293 ? Ss 0:17 0 3260 40551 27004 0.6 postgres: writer process 4294 ? Ss 0:00 0 3260 9363 1744 0.0 postgres: stats collector process 14508 ? Ss 0:01 0 3260 41195 29356 0.7 postgres: me csdb zim(48570) notify interrupt 20701 ? Ss 0:01 0 3260 41127 29384 0.7 postgres: others csdb chef(45882) notify interrupt 31179 ? Ss 0:01 0 3260 41127 29428 0.7 postgres: others csdb yfandes(33113) notify interrupt 7342 ? Ss 0:03 0 3260 41723 30584 0.7 postgres: others csdb reed(54823) notify interrupt 7343 ? Ss 0:02 0 3260 41127 29396 0.7 postgres: others csdb reed(54824) notify interrupt 7404 ? Ss 0:02 0 3260 41127 29392 0.7 postgres: others csdb reed(54830) notify interrupt 29537 ? Ss 0:02 0 3260 41127 29404 0.7 postgres: others csdb stupid(60028) notify interrupt 26671 pts/0 S+ 0:00 1 19 7976 1700 0.0 su postgres -c /s/postgresql-8.2/bin/pg_ctl stop -m fast -D /scratch.1/postgres/csdb-8.2 -l /dev/null 26672 pts/0 S+ 0:00 1 283 5556 1180 0.0 -csh -c /usr/bin/pg_ctl stop -m fast -D /scratch.1/postgres/csdb- 8.2 -l /dev/null 26673 pts/0 S+ 0:00 0 23 6916 1440 0.0 /usr/bin/pg_ctl stop -m fast -D /postgres/db-8.2 -l /dev/null 26713 ttyS0 S+ 0:00 0 71 5016 644 0.0 grep post Any idea how postgres gets into this state, or how it can be resolved short of a system reboot or a "stop -m immediate"? Thanks much. Peter ------=_Part_86943_6288173.1179784648903 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all, I'm having some trouble restarting a long-running server. Basically, pg_ctl can't kill any processes waiting on a notify interrupt. Here's what happened after trying a "stop -m fast"

[root@vero ~]# ps axvw | grep post
 3606 ?        S      3:30     23  3260 41575 6644  0.1 /usr/bin/postgres -D /postgres/db-8.2
 4293 ?        Ss     0:17      0  3260 40551 27004  0.6 postgres: writer process
 4294 ?        Ss     0:00      0  3260  9363 1744  0.0 postgres: stats collector process
14508 ?        Ss     0:01      0  3260 41195 29356  0.7 postgres: me csdb zim(48570) notify interrupt
20701 ?        Ss     0:01      0  3260 41127 29384  0.7 postgres: others csdb chef(45882) notify interrupt
31179 ?        Ss     0:01      0  3260 41127 29428  0.7 postgres: others csdb yfandes(33113) notify interrupt
 7342 ?        Ss     0:03      0  3260 41723 30584  0.7 postgres: others csdb reed(54823) notify interrupt
 7343 ?        Ss     0:02      0  3260 41127 29396  0.7 postgres: others csdb reed(54824) notify interrupt
 7404 ?        Ss     0:02      0  3260 41127 29392  0.7 postgres: others csdb reed(54830) notify interrupt
29537 ?        Ss     0:02      0  3260 41127 29404  0.7 postgres: others csdb stupid(60028) notify interrupt
26671 pts/0    S+     0:00      1    19  7976 1700  0.0 su postgres -c /s/postgresql-8.2/bin/pg_ctl stop -m fast -D /scratch.1/postgres/csdb-8.2 -l /dev/null
26672 pts/0    S+     0:00      1   283  5556 1180  0.0 -csh -c /usr/bin/pg_ctl stop -m fast -D /scratch.1/postgres/csdb- 8.2 -l /dev/null
26673 pts/0    S+     0:00      0    23  6916 1440  0.0 /usr/bin/pg_ctl stop -m fast -D /postgres/db-8.2 -l /dev/null
26713 ttyS0    S+     0:00      0    71  5016  644  0.0 grep post

Any idea how postgres gets into this state, or how it can be resolved short of a system reboot or a "stop -m immediate"? Thanks much.

Peter
------=_Part_86943_6288173.1179784648903--