Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 1F47CB5DBCB for ; Mon, 27 Jun 2011 09:25:57 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 75804-01 for ; Mon, 27 Jun 2011 12:25:50 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp162.dfw.emailsrvr.com (smtp162.dfw.emailsrvr.com [67.192.241.162]) by mail.postgresql.org (Postfix) with ESMTP id C9335B5D94C for ; Mon, 27 Jun 2011 09:25:50 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 43CB22701D1; Mon, 27 Jun 2011 08:25:50 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp6.relay.dfw1a.emailsrvr.com (Authenticated sender: adarsh.sharma-AT-orkash.com) with ESMTPSA id 1ABE22701E5; Mon, 27 Jun 2011 08:25:48 -0400 (EDT) Message-ID: <4E0876C8.7050200@orkash.com> Date: Mon, 27 Jun 2011 17:55:44 +0530 From: Adarsh Sharma User-Agent: Thunderbird 2.0.0.22 (X11/20090625) MIME-Version: 1.0 To: =?UTF-8?B?ScOxaWdvIE1hcnRpbmV6IExhc2FsYQ==?= CC: pgsql-admin@postgresql.org Subject: Re: Urgent! Log full with inexistent PID processes References: <1309174277.5158.30.camel@deimos> In-Reply-To: <1309174277.5158.30.camel@deimos> Content-Type: multipart/alternative; boundary="------------030009020105010509000200" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201106/143 X-Sequence-Number: 37769 This is a multi-part message in MIME format. --------------030009020105010509000200 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Iñigo Martinez Lasala wrote: > Hi everybody. > > We have a postgres 8.4.5-2 database under Debian Lenny 64bit. > This database has been working without any problem, but this afternoon > server has got out of space due to a log dump. > > Log file gets full with this entry until it reaches several gigabytes: > > 2011-06-27 13:25:07 CEST LOG: PID 21822 in cancel request did not > match any process > 2011-06-27 13:25:07 CEST LOG: PID 21821 in cancel request did not > match any process > 2011-06-27 13:25:07 CEST LOG: PID 21820 in cancel request did not > match any process > 2011-06-27 13:25:07 CEST LOG: PID 21816 in cancel request did not > match any process > 2011-06-27 13:25:07 CEST LOG: PID 21802 in cancel request did not > match any process > > First check the space occupied by pg_log directory. Just delete the previous logs that are 1 month older. rm -rf pg_log****** > Of course, we have restarted postmaster and rebooted machine but > problem remains. > > Any clue about this? > > pg_hba only allows connection from localhost and, of course, there are > no processes with these PIDs in the server... > > Thanks in advance. --------------030009020105010509000200 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Iñigo Martinez Lasala wrote:
Hi everybody.

We have a postgres 8.4.5-2 database under Debian Lenny 64bit.
This database has been working without any problem, but this afternoon server has got out of space due to a log dump.

Log file gets full with this entry until it reaches several gigabytes:

2011-06-27 13:25:07 CEST LOG:  PID 21822 in cancel request did not match any process
2011-06-27 13:25:07 CEST LOG:  PID 21821 in cancel request did not match any process
2011-06-27 13:25:07 CEST LOG:  PID 21820 in cancel request did not match any process
2011-06-27 13:25:07 CEST LOG:  PID 21816 in cancel request did not match any process
2011-06-27 13:25:07 CEST LOG:  PID 21802 in cancel request did not match any process


First check the space occupied by pg_log directory.
Just delete the previous logs that are 1 month older.
rm -rf pg_log******


Of course, we have restarted postmaster and rebooted machine but problem remains.

Any clue about this?

pg_hba only allows connection from localhost and, of course, there are no processes with these PIDs in the server...

Thanks in advance. 

--------------030009020105010509000200--