Re: Urgent! Log full with inexistent PID processes

From: Adarsh Sharma <adarsh(dot)sharma(at)orkash(dot)com>
To: Iñigo Martinez Lasala <imartinez(at)vectorsf(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Urgent! Log full with inexistent PID processes
Date: 2011-06-27 12:25:44
Message-ID: 4E0876C8.7050200@orkash.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Florian Weimer 2011-06-27 13:40:49 Re: Urgent! Log full with inexistent PID processes
Previous Message Iñigo Martinez Lasala 2011-06-27 11:31:17 Urgent! Log full with inexistent PID processes