Message-ID: <39899E30.7F07B044@wgcr.org>
Date: Thu, 03 Aug 2000 12:30:40 -0400
From: Lamar Owen <lamar.owen@wgcr.org>
MIME-Version: 1.0
To: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
CC: csawtell@xtra.co.nz, Thomas Lockhart <lockhart@alumni.caltech.edu>,
	pgsql-interfaces@postgresql.org, Oliver Elphick <olly@lfix.co.uk>
Subject: Re: Re: And Furthermore. Was: PSQL Working, but PGAccess
	Not Connecting.
References: <001c01bffc2b$e5800970$cf597bd8@WORKGROUP>
	<00080218510600.11047@berty>
	<002e01bffd11$e04b0ef0$ae637bd8@WORKGROUP>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

David Lloyd-Jones wrote:
> 
> From: "Christopher Sawtell" <csawtell@xtra.co.nz>
> > On Wed, 02 Aug 2000, David Lloyd-Jones wrote:
> > > "David Lloyd-Jones" <david.lloyd-jones@netcom.ca> wrote:
> > > > How can this be? Isn't this a contradiction of some sort?
> > > Contradiction. so what else is new?

> > I get that situation too. There is something strangely amiss with the
> pg_ctrl
> > script. I just do not use it.
 
> Dunno about that: I was starting up with Lamar Owen's postgresql start|stop
> script, so the pg_ctrl thing doesn't apply, does  it?

Yes, it does for 7.0.2's script.  And it's pg_ctl, with no r.
 
> See Tom Lane's plausible explanation a couple of days ago in this thread.

First, try to ping localhost and see what happens.  If that doesn't
work, you have a basic network misconfiguration somewhere you're going
to have to trace down.

Next,`attempt to telnet to localhost -- if that doesn't work, you still
have a network problem.

Postmaster can't listen on a nonexistent network interface, even with
-i.

This may also explain AOLserver not listening on port 80 -- what does
AOLserver's error log say about where nssock is listening?

To check for Apache installation, use 'rpm -qa|grep apache'....
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11