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

yua **<azuneko@hotmail.com> wrote:

> PostgreSQL 8.3.3 on i386-portbld-freebsd7.0, compiled by GCC cc
(GCC)
> 4.2.1 20070719  [FreeBSD]

>    postgres[681]: [506-1] WARNING:  worker took too long to start;
cancelled
> Nov 12 11:15:12 kddi-nwmgr01 postgres[681]:
> [507-1] WARNING:  worker took too long to start; cancelled

> ps -auxeww
> ---------+---------+---------+---------+---------+---------+--------
> USER    PID %CPU %MEM   VSZ   RSS  TT  STAT STARTED      TIME
COMMAND
> pgsql   682 99.0  0.1  9336  2740  ??  Rs   27Nov08 343573:19.27
USER=pgsql

> Q6 PostgreSQL Programs
> A6 php5-pdo_pgsql-5.2.12
>      p5-DBD-Pg-2.16.0

> Q8 OS Version
> A8 FreeBSD 7.0-RELEASE-p2

> CPU : Intel, Xeon2.4
> RAM : 2GB
> Storage
>  RAID Card : LSI MegaRAID
>  Battery Cache : YES
>  write-back Cache : NO
>  Software RAID : NO ( Hardware RAID)
>  SAN : NO
>  Disk : 7,200rpm SATA 3lot
>  Disk : RAID5 3slot

This is starting to sound like some other reports from FreeBSD.

http://archives.postgresql.org/pgsql-general/2008-06/msg00934.php

http://archives.postgresql.org/pgsql-general/2010-01/msg01076.php

Unfortunately, the other posters didn't post back with information
on resolution of the issue.  Could you read Tom's advice and report
back?:

http://archives.postgresql.org/pgsql-general/2010-01/msg01079.php

-Kevin