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

On Mon, Jan 18, 2010 at 12:43 AM, azuneko <azuneko@hotmail.com> wrote:
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A05284
> Logged by: =A0 =A0 =A0 =A0 =A0azuneko
> Email address: =A0 =A0 =A0azuneko@hotmail.com
> PostgreSQL version: 8.3.3
> Operating system: =A0 FreeBSD7.0.2
> Description: =A0 =A0 =A0 =A0Postgres 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 postg=
res
> 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.
> =A0 =A0 =A0 =A0WARNING: =A0worker 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;
> =A0 =A0 =A0 =A0Software
> =A0 =A0 =A0 =A0 -OS : FreeBSD 7.0.2
> =A0 =A0 =A0 =A0 -Postgres version : 8.3.3
> =A0 =A0 =A0 =A0Hardware
> =A0 =A0 =A0 =A0 -Disk configuration : RAID5 (MegaCLI)
> =A0 =A0 =A0 =A0 -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