X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id CBFAC53961 for ; Thu, 21 Apr 2005 10:54:08 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 82532-07 for ; Thu, 21 Apr 2005 13:54:03 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by svr1.postgresql.org (Postfix) with ESMTP id 0BB565397E for ; Thu, 21 Apr 2005 10:54:02 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 70so601323wra for ; Thu, 21 Apr 2005 06:54:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=AwGAvVfjyYPWkYmid2VmbhjJZUdNUzNknqwLHBCerSkd7wWr1pOmVMPXf70+xWtTLsKISUlYtCcAvGAoDdpbES9OtWvM9vv751L4/8hrtDqA1FkYriQe37H+YAUTD57Y0Sa+ji6+/nI1NfyvbBzqbYK6YEiqOjMRPShVeIMlBU4= Received: by 10.54.15.30 with SMTP id 30mr2130182wro; Thu, 21 Apr 2005 06:53:38 -0700 (PDT) Received: by 10.54.10.75 with HTTP; Thu, 21 Apr 2005 06:53:37 -0700 (PDT) Message-ID: <46a1632105042106536eb90ebf@mail.gmail.com> Date: Thu, 21 Apr 2005 09:53:37 -0400 From: Bobb Shields Reply-To: Bobb Shields To: pgsql-admin@postgresql.org Subject: Re: Troubleshooting Postgres7.4 In-Reply-To: <20050420150817.GA75226@winnie.fuhr.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_219_13768425.1114091617008" References: <46a1632105041911115fafc703@mail.gmail.com> <20050420150817.GA75226@winnie.fuhr.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.625 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, HTML_20_30, HTML_MESSAGE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/297 X-Sequence-Number: 17310 ------=_Part_219_13768425.1114091617008 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'm using two php apps on my website that I'm serving on the same linux box= =20 (FC3). Both titles (phpbb, tikipro) report that they cannot connect to the= =20 database. I believe the updates were php code updates. I downloaded them via yum when= =20 I noticed my up2date blinking. ps ax | grep postmaster does not return anything. I don't know what it=20 should return anyways... I tried to start postgres by su'ing from root to " - postgres", and running= =20 postmaster. I get an error that says that the lock file already exists, and= =20 asks whether another instance of postmaster is already running. Service Configuration once again reports that it is stopped, and I can't=20 connect via pgAdmin3. How can I check what the last updates were from yum? My command that I ran= =20 was "yum -y update"=20 Thanks! ~Bobb=20 On 4/20/05, Michael Fuhr wrote:=20 >=20 > On Tue, Apr 19, 2005 at 02:11:47PM -0400, Bobb Shields wrote: > > > > I'm running 7.4, and I recently did a few upgrades, which seem to have > > broken it. >=20 > Could you expand on "seem to have broken it"? What are you doing > and what unexpected behavior or error messages are you seeing? >=20 > > I believe that all of them were php updates. >=20 > What exactly did you change? The version of PHP? Application code > written in PHP? Something else, like settings in postgresql.conf? >=20 > > Anywho, my service configuration shows that postmaster is stopped. I > > can't find an instance of it in my system monitor. > > > > Can you help me to figure out if its still running, and if its not, why= =20 > it > > won't start like it should? >=20 > You could use ps from a shell prompt to verify whether the postmaster > is running. For example, "ps ax | grep postmaster" should work on > your system (you said you were using Linux). >=20 > Try to start the postmaster from the shell and see what happens. > If it doesn't start but you see nothing on the screen, then look > through postgresql.conf and the PostgreSQL startup script to see > where log messages are going, then look through those messages to > see what's happening. >=20 > As I recall, some PostgreSQL packages for Linux redirect the > postmaster's output to /dev/null -- if this is the case on your > system, then I'd suggest changing that so you can see startup errors. >=20 > -- > Michael Fuhr > http://www.fuhr.org/~mfuhr/ > ------=_Part_219_13768425.1114091617008 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'm using two php apps on my website that I'm serving on the same linux box= (FC3).  Both titles (phpbb, tikipro) report that they cannot connect = to the database.

I believe the updates were php code updates.  = I downloaded them via yum when I noticed my up2date blinking.

ps ax | grep postmaster does not return anything.  I don't kno= w what it should return anyways...

I tried to start postgres by su'i= ng from root to " - postgres", and running postmaster.  I ge= t an error that says that the lock file already exists, and asks whether an= other instance of postmaster is already running.

Service Configuration once again reports that it is stopped, and I = can't connect via pgAdmin3.

How can I check what the last updates we= re from yum?  My command that I ran was "yum -y update"
=
Thanks!
~Bobb

On 4/20/05, = Michael Fuhr <mike@fuhr.org>= wrote:
On Tue, Apr 19, 2005 at 02:11:47= PM -0400, Bobb Shields wrote:
>
> I'm running 7.4, and I recent= ly did a few upgrades, which seem to have
> broken it.

Could you expand on "seem to have broken it= "?  What are you doing
and what unexpected behavior or er= ror messages are you seeing?

> I believe that all of them were ph= p updates.

What exactly did you change?  The version of PHP? &n= bsp;Application code
written in PHP?  Something else, like set= tings in postgresql.conf?

> Anywho, my service configuration show= s that postmaster is stopped. I
> can't find an instance of it in my system monitor.
>
>= Can you help me to figure out if its still running, and if its not, why it=
> won't start like it should?

You could use ps from a shell p= rompt to verify whether the postmaster
is running.  For example, "ps ax | grep postmaster"= should work on
your system (you said you were using Linux).

Try = to start the postmaster from the shell and see what happens.
If it doesn= 't start but you see nothing on the screen, then look
through postgresql.conf and the PostgreSQL startup script to see
whe= re log messages are going, then look through those messages to
see what'= s happening.

As I recall, some PostgreSQL packages for Linux redirec= t the
postmaster's output to /dev/null -- if this is the case on your
syst= em, then I'd suggest changing that so you can see startup errors.

--=
Michael Fuhr
http://www.fuhr= .org/~mfuhr/

------=_Part_219_13768425.1114091617008--