Skip site navigation (1) Skip section navigation (2)

Re: BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown

From: yua ゅぁ <azuneko(at)hotmail(dot)com>
To: <robertmhaas(at)gmail(dot)com>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown
Date: 2010-01-19 10:26:10
Message-ID: KAW101-W3357249F21DE723E6DA1CAAE650@phx.gbl (view raw or flat)
Thread:
Lists: pgsql-bugs
Hello.

 

>You haven't really provided us with much detail here, but it kind of
>sounds like your system is overloaded.
>...Robert

Thank you for your kindness.
Following modules are used 
 mod_auth_pgsql-2.0.3_1
 postgresql-client-8.3.9_1,1
 postgresql-server-8.3.9_1
 p5-DBD-Pg-2.16.0
 php5-pdo_pgsql-5.2.12

What kind of information shall, I geve you in addtion to the list
above?
 
> Date: Mon, 18 Jan 2010 15:33:02 -0500
> Subject: Re: [BUGS] BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown
> From: robertmhaas(at)gmail(dot)com
> To: azuneko(at)hotmail(dot)com
> CC: pgsql-bugs(at)postgresql(dot)org
> 
> On Mon, Jan 18, 2010 at 12:43 AM, azuneko <azuneko(at)hotmail(dot)com> wrote:
> > The following bug has been logged online:
> >
> > Bug reference:      5284
> > Logged by:          azuneko
> > Email address:      azuneko(at)hotmail(dot)com
> > PostgreSQL version: 8.3.3
> > Operating system:   FreeBSD7.0.2
> > Description:        Postgres CPU 100% and worker took too long to start;
> > cancelled... Systemdown
> > Details:
> >
> > Hello,
> >
> > I have the following 2 problems.
> > It would be appreciated if you give me some information such as the way to
> > avoid them.(Or if those problems are already known and fixed, could you
> > please tell me what version I should apply.)
> >
> > 1,CPU utilization of postgres reaches 100%.
> >
> > I excuted "top" command and sometimes found that CPU utilization of postgres
> > process reached 100% or almost 100%. (This is similar to the problem that
> > was posted at
> > http://archives.free.net.ph/message/20081104.074244.6e0dbcde.ja.html.)
> > What might be the cause?
> >
> > 2. The following warning can be seen in the postgres log.
> >        WARNING:  worker took too long to start; cancelled
> >
> > After this warning firstly appears in the log, the same warining message
> > seems to be repeated. And if you leave this state as it is, the OS freezes
> > before long. I guess this event happens because the daemons related to
> > postgres (such as vacuum and autovacuum) won't release the shared memory and
> > exclusively keep using it. Am I correct?
> >
> > Those 2 problems are confirmed to happen at least under the following
> > conditions;
> >        Software
> >         -OS : FreeBSD 7.0.2
> >         -Postgres version : 8.3.3
> >        Hardware
> >         -Disk configuration : RAID5 (MegaCLI)
> >         -CPU : Xeon2.4
> >
> > Thank you.
> 
> You haven't really provided us with much detail here, but it kind of
> sounds like your system is overloaded.
> 
> ...Robert
 		 	   		  
_________________________________________________________________
【無料!】マイクロソフト公式メーラーで、メールを一括チェック
http://windows7.jp.msn.com/master/windows_live/

In response to

Responses

pgsql-bugs by date

Next:From: WildWezyrDate: 2010-01-19 11:07:24
Subject: BUG #5289: Unpredictable error in plpgsql function loop
Previous:From: Jon Erdman (aka StuckMojo)Date: 2010-01-19 05:09:00
Subject: BUG #5288: Restoring a 7.4.5 -Fc dump using -j 2 segfaults (patch included)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group