Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 15FD21337C23 for ; Thu, 5 May 2011 14:17:06 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 45649-01-8 for ; Thu, 5 May 2011 17:16:57 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mailgate.iii.com (mailgate.iii.com [205.227.88.3]) by mail.postgresql.org (Postfix) with ESMTP id 5DC381337BF8 for ; Thu, 5 May 2011 14:16:48 -0300 (ADT) Received: from mailhub.iii.com (mailhub [10.1.2.3]) by mailgate.iii.com (8.13.6/8.13.6) with ESMTP id p45H89ff009072 for ; Thu, 5 May 2011 10:08:09 -0700 (PDT) Received: from [10.1.7.210] ([10.1.7.210]) by mailhub.iii.com (8.13.6/8.13.6) with ESMTP id p45HKRc0031062; Thu, 5 May 2011 10:20:27 -0700 (PDT) Message-ID: <4DC2DB7A.3050609@iii.com> Date: Thu, 05 May 2011 10:16:42 -0700 From: Dinesh Bhandary Reply-To: dbhandary@iii.com Organization: Innovative Interfaces User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: dbhandary@iii.com CC: pgsql-admin@postgresql.org Subject: Re: worker took too long to start; cancelled ( postgres 9.0.3) References: <4DC1CB6E.3000309@iii.com> In-Reply-To: <4DC1CB6E.3000309@iii.com> Content-Type: multipart/alternative; boundary="------------090406070007070008000203" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.909 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201105/59 X-Sequence-Number: 37496 This is a multi-part message in MIME format. --------------090406070007070008000203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi All - I am reposting my earlier message. I saw someone had the same problem that I had, but I could not see the resolution. Please let me know if you have more info on this. Here is the thread that talks about the same problem. 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 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 On 5/4/2011 2:55 PM, Dinesh Bhandary wrote: > Hi All - > > I am getting the following error while starting postgres 9.0.3. And > when it happens I could not establish new connections and the > following error messages keeps on coming up. > Are you guys aware of this problem? Is it a bug? It has happened to me > twice already. We are running this on red hat 5.6. > > "worker took too long to start; cancelled" > > Thanks. > > Dinesh > --------------090406070007070008000203 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi All - I am reposting my earlier message. I saw someone had the same problem that I had, but I could not see the resolution. Please let me know if you have more info on this.

Here is the thread that talks about the same problem. 


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


On 5/4/2011 2:55 PM, Dinesh Bhandary wrote:
Hi All -

I am getting the following error while starting postgres 9.0.3. And when it happens I could not establish new connections and the following error messages keeps on coming up.
Are you guys aware of this problem? Is it a bug? It has happened to me twice already. We are running this on red hat 5.6.

"worker took too long to start; cancelled"

Thanks.

Dinesh


--------------090406070007070008000203--