Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 46A9F475EE2 for ; Sat, 11 May 2002 12:00:30 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id B7D7B475D11 for ; Sat, 11 May 2002 12:00:17 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g4BFxjW13065; Sat, 11 May 2002 11:59:45 -0400 (EDT) To: "Rajesh Kumar Mallah." Cc: pgsql-sql@postgresql.org, Jan Wieck Subject: Re: Further info : Very high load average but no cpu utilization ? In-reply-to: <200205111035.05281.mallah@trade-india.com> References: <200205111007.47338.mallah@trade-india.com> <200205111035.05281.mallah@trade-india.com> Comments: In-reply-to "Rajesh Kumar Mallah." message dated "Sat, 11 May 2002 10:35:05 +0530" Date: Sat, 11 May 2002 11:59:44 -0400 Message-ID: <13062.1021132784@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200205/109 X-Sequence-Number: 7745 "Rajesh Kumar Mallah." writes: > [root@linux10320 root2]# ps auxwww| grep post > postgres 1131 0.0 0.0 139424 4 ? D May1004/usr/local/pgsql/bin/postmaster > postgres 1132 0.0 0.0 140412 4 ? D May10 0:13 postgres: stats buffer process > postgres 1133 0.0 0.0 139576 4 ? S May10 0:18 postgres: stats collector process > postgres 8046 0.0 0.0 238712 4 ? D 00:25 0:13 postgres: tradein tradein_clients 130.94.20.27 SELECT > postgres 8089 0.0 0.0 139812 4 ? D 00:26 0:00 postgres: checkpoint subprocess > postgres 11442 0.0 0.0 218152 4 ? D 04:25 0:03 postgres: tradein tradein_clients 130.94.20.27 SELECT > postgres 15453 0.1 0.0 0 0 ? Z 08:17 0:09 [postmaster ] > postgres 15455 0.0 0.0 0 0 ? Z 08:17 0:00 [postmaster ] > postgres 15456 0.0 0.0 0 0 ? Z 08:18 0:00 [postmaster ] > postgres 15457 0.0 0.0 0 0 ? Z 08:19 0:00 [postmaster ] > postgres 15462 0.0 0.0 0 0 ? Z 08:20 0:01 [postmaster ] I think your postmaster is stuck; it should have reaped those defunct subprocesses instantly. Given that you also seem to have a stuck checkpoint process (8 hours to run a checkpoint?) there is probably something hosed in the interprocess communication logic, but it's hard to guess what from this amount of info. At this point probably your best bet is to kill all the running postgres processes (try SIGTERM first, then SIGKILL if that doesn't work) and launch a postmaster from a fresh start. Don't forget the ulimit this time. regards, tom lane