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

Re: Too much postmaster prozesses / CPU near 100%

From: "Josh Berkus" <josh(at)agliodbs(dot)com>
To: "Roth, Michael J(dot)" <MichaelRoth(at)schmuecker(dot)de>, "'Josh Berkus'" <josh(at)agliodbs(dot)com>, "'pgsql-novice(at)postgresql(dot)org'" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Too much postmaster prozesses / CPU near 100%
Date: 2001-10-29 16:24:08
Message-ID: web-494065@davinci.ethosmedia.com (view raw or flat)
Thread:
Lists: pgsql-novice
Michael,

> Maybe i dont have exactly described our Problem:
> 
> With our "old" Server (MMX-233, 256MB RAM, Linux 2.2.16, Postgres
> 7.0.3)
> we dont had any Probs.
> After we run the new Server, some hours all things are ok.
> And then, suddenly the machine creates many postmaster-processes in
> a few seconds. Other System-Functions works now likewise not correct
> (top: CPU-Idle 62985,2 %; /etc/init.d/postmaster stop = failed;
> but /etc/init.d/postmaster start = postmaster already running; 
> "/proc not mounted"; "too many open files in system"; <-- examples)
> We must "crash" the postmaster (kill -15 or kill-9) and restart
> apache
> and start postmaster again.
> And then, all things works correct again for some time (minutes or
> hours).
> (Info: we run vacuumdb 1-2 times a day). 

Hmmm ... double-check your postgresql.conf parameters, and log at a high
debug level when you start up.  I once had a similar problem to this (on
7.1.0) that was a result of bad (conflicting) postgresql.conf parameters
I had set.  PostgreSQL kept starting and spawning extra processes, but
was not accessable from psql.

> I think, the problem is handling of shared memory either in Postgres
> 7.1.3
> or in Kernel 2.4.x or both.

I doubt it's that simple, although you may check your *specific* kernel
version ... the reason why 2.4.x has been upgraded so many times in the
last 7 months is to fix bugs.  I have been using 2.4.4. with no
problems.  So, steps from here:

1. Restart the postgresql server at a high debug level, checking the
logs carefully for bootup and/or broken connection errors.
2. Re-install the server, reverting to 2.2.18 to see if it's a
kernel-specific problem.  Or upgrade to 2.4.13, either way.
3. Contact SuSE professional services to see if they can help you.
They're expensive, but good and you won't have the language barrier.

> Don't know how to fix the Prob. Consultants from Hewlett-Packard AND
> RedHat don't know too. Info: Our new Server HP-LC2000r is certified
> with RedHat7.1 and does NOT run with kernel 2.2.x :-((

Hmmm.  Have you tried getting RedHat to refer you to their RHDB
division?  Those people should be intimately familiar with PostgreSQL.
I wouldn't expect HP to know anything, myself.

-Josh Berkus


______AGLIO DATABASE SOLUTIONS___________________________
                                       Josh Berkus
  Complete information technology      josh(at)agliodbs(dot)com
   and data management solutions       (415) 565-7293
  for law firms, small businesses        fax 621-2533
    and non-profit organizations.      San Francisco

In response to

pgsql-novice by date

Next:From: Tom LaneDate: 2001-10-29 17:30:13
Subject: Re: Triggers failing from 7.0.2 to 7.1.3
Previous:From: Roth, Michael J.Date: 2001-10-29 09:26:24
Subject: Re: Too much postmaster prozesses / CPU near 100%

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