pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Re: PSQL Working, but PGAccess Not Connecting.
18+ messages / 10 participants
[nested] [flat]

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-30 19:23  David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  0 siblings, 1 reply; 18+ messages in thread

From: David Lloyd-Jones @ 2000-07-30 19:23 UTC (permalink / raw)
  To: pgsql-interfaces

I am trying to create a database which will eventually become part of a
dynamic Web page put up by AOLserver within .adp pages. This is all running
on Linux 6.2 on a machine with 64 meg of RAM and plenty of
disk.etc/rc/d/init.

I can access it with the command psql <databasename>, which is nice, but
PGAccess, the GUI, refuses to open it. The open command gives me the error
message "Connection to database failed connect DBStart() -- connect()
failed: network is unreachable
Is the postmaster running (with -i) at "localhost" and accepting connections
on TCP/IP port '5432'?"

I do not know whther I am running the postmaster with -i. I started it with
the command /etc/rc.d/init.d/postgresql start. I have also tried start -i.
In both cases I get the response that postmaster is running -- which is why
psql works.

Netscape is refused by http://127.0.0.1 and by http://127.0.0.1:5432.  What
should I be doing about this "network is unreachable" or the "DBStart() --
connect failed"?

                                          Many thanks,

                                                          -dlj.






^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-30 21:40  Tom Lane <tgl@sss.pgh.pa.us>
  parent: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  0 siblings, 1 reply; 18+ messages in thread

From: Tom Lane @ 2000-07-30 21:40 UTC (permalink / raw)
  To: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; +Cc: pgsql-interfaces

"David Lloyd-Jones" <david.lloyd-jones@attcanada.ca> writes:
> PGAccess, the GUI, refuses to open it. The open command gives me the error
> message "Connection to database failed connect DBStart() -- connect()
> failed: network is unreachable
          ^^^^^^^^^^^^^^^^^^^^^^

Your networking configuration is broken: the kernel does not believe it
can contact itself.  I can't give you much help about specific fixes,
but until you can do local loopback (such as "telnet 127.0.0.1") you
won't have any luck contacting the postmaster via TCP --- which is
what PGAccess wants to do.

I'd suggest reading some basic networking HOWTOs ...

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-30 22:21  David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 18+ messages in thread

From: David Lloyd-Jones @ 2000-07-30 22:21 UTC (permalink / raw)
  To: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-interfaces

"Tom Lane" <tgl@sss.pgh.pa.us> writes


> "David Lloyd-Jones" <david.lloyd-jones@attcanada.ca> writes:
> > PGAccess, the GUI, refuses to open it. The open command gives me the
error
> > message "Connection to database failed connect DBStart() -- connect()
> > failed: network is unreachable
>           ^^^^^^^^^^^^^^^^^^^^^^
> Your networking configuration is broken: the kernel does not believe it
> can contact itself.  I can't give you much help about specific fixes,
> but until you can do local loopback (such as "telnet 127.0.0.1") you
> won't have any luck contacting the postmaster via TCP --- which is
> what PGAccess wants to do.
>
> I'd suggest reading some basic networking HOWTOs ...
>

Tom,

Thanks for your note. Not to be ungracious, (RTFM would always be good
advice, were it not for the fact that manuals are written at greater speed
than one can read them) but I don't see how this adds up: I'm not on a
network, and PSQL, which is a front end to PostgreSQL, just like PGAccess is
supposed to be, is running fine.

Let me rephrase the question this way: since PSQL works, why wouldn't
PGAccess?

                                   Cheers,

                                             -dlj.




^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-30 22:34  Tom Lane <tgl@sss.pgh.pa.us>
  parent: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  0 siblings, 3 replies; 18+ messages in thread

From: Tom Lane @ 2000-07-30 22:34 UTC (permalink / raw)
  To: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; +Cc: pgsql-interfaces

"David Lloyd-Jones" <david.lloyd-jones@attcanada.ca> writes:
> than one can read them) but I don't see how this adds up: I'm not on a
> network, and PSQL, which is a front end to PostgreSQL, just like PGAccess is
> supposed to be, is running fine.

By default, psql connects via a Unix-socket path, not by TCP.  PGAccess
is written differently and always tries to connect by TCP.  If you try
to start psql with "-h localhost" or some such, it will try TCP and
fail in the same way ...

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 01:54  Red Pineseed <yue207@home.com>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  2 siblings, 2 replies; 18+ messages in thread

From: Red Pineseed @ 2000-07-31 01:54 UTC (permalink / raw)
  To: ; +Cc: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; pgsql-interfaces

It looks like you don't have the user permission set up
properly. Here is a jpg much like what you have descrbibed
in the message. What the postmaster is not running in the
background or the user permission is not set properly, you
get a message like that. 

use the createuser command to create user and set proper
permision and connect the db like.

Philip


Tom Lane wrote:
> 
> "David Lloyd-Jones" <david.lloyd-jones@attcanada.ca> writes:
> > than one can read them) but I don't see how this adds up: I'm not on a
> > network, and PSQL, which is a front end to PostgreSQL, just like PGAccess is
> > supposed to be, is running fine.
> 
> By default, psql connects via a Unix-socket path, not by TCP.  PGAccess
> is written differently and always tries to connect by TCP.  If you try
> to start psql with "-h localhost" or some such, it will try TCP and
> fail in the same way ...
> 
>                         regards, tom lane

Attachments:

pgsql_error.jpg (image/jpeg, 23.7K) download view image
^ permalink raw reply [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 03:42  Mike Mascari <mascarm@mascari.com>
  parent: Red Pineseed <yue207@home.com>
  1 sibling, 0 replies; 18+ messages in thread

From: Mike Mascari @ 2000-07-31 03:42 UTC (permalink / raw)
  To: Red Pineseed <yue207@home.com>; +Cc: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; pgsql-interfaces

Red Pineseed wrote:
> 
> It looks like you don't have the user permission set up
> properly. Here is a jpg much like what you have descrbibed
> in the message. What the postmaster is not running in the
> background or the user permission is not set properly, you
> get a message like that.
> 
> use the createuser command to create user and set proper
> permision and connect the db like.
> 
> Philip

Except that there's a difference between "Connection refused",
which is typical of the postmaster not being started with the -i
option, and "Network unreachable", which is typical of a TCP/IP
application where the kernel cannot resolve the route to the
destination host. The user never did specify the success/failure
of testing loop-back via telnet on 127.0.0.1. My bet is it didn't
work. My money's on Tom Lane.

Mike Mascari



^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 04:17  David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  parent: Red Pineseed <yue207@home.com>
  1 sibling, 1 reply; 18+ messages in thread

From: David Lloyd-Jones @ 2000-07-31 04:17 UTC (permalink / raw)
  To: Red Pineseed <yue207@home.com>; Mike Mascari <mascarm@mascari.com>; +Cc: pgsql-interfaces

"Red Pineseed" <yue207@home.com>. wrote:


> It looks like you don't have the user permission set up
> properly. Here is a jpg much like what you have descrbibed
> in the message. What the postmaster is not running in the
> background or the user permission is not set properly, you
> get a message like that.
>
> use the createuser command to create user and set proper
> permision and connect the db like.

Philip,

Thanks for your note. PostgreSQL starts with a default user named Postgres,
as far as I know. (Does anybody know its password? I've been assuming it's
either 'postgres' or null.)

Mike Mascari wrote:

Except that there's a difference between "Connection refused",
which is typical of the postmaster not being started with the -i
option, and "Network unreachable", which is typical of a TCP/IP
application where the kernel cannot resolve the route to the
destination host. The user never did specify the success/failure
of testing loop-back via telnet on 127.0.0.1. My bet is it didn't
work. My money's on Tom Lane.

Mike,

I did try the loopback, as I mentioned in a note to Tom (perhaps off-line,
sorry.)
Agreed, his explanation makes sense, and I'm looking for the right place to
put the -i.

Anybody know the innards of that /etc/rc.d/init.d/postgresql start
batchfile?

                                                                         -dl
j.









^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 04:53  Mike Mascari <mascarm@mascari.com>
  parent: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  0 siblings, 0 replies; 18+ messages in thread

From: Mike Mascari @ 2000-07-31 04:53 UTC (permalink / raw)
  To: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; +Cc: Red Pineseed <yue207@home.com>; pgsql-interfaces

David Lloyd-Jones wrote:
> 
> I did try the loopback, as I mentioned in a note to Tom (perhaps off-line,
> sorry.)
> Agreed, his explanation makes sense, and I'm looking for the right place to
> put the -i.
> 
> Anybody know the innards of that /etc/rc.d/init.d/postgresql start
> batchfile?

The older RPMS started the postmaster without the -i for security
reasons. However, the newer ones do start it up with TCP/IP
support enabled by default. Which rpms are you using? You should
look for a line like:

su -l postgres -c '/usr/bin/postmaster -o -F -i -S
-D/var/lib/pgsql'

The -o -F flag combination turns off fsync. The -i switch will
enable the TCP/IP connection. -S says to start up in silent mode.
-D specifies the location of the where the data/base hierarchy is
stored. If I recall the older RPMS correctly, they will have a
line like:

su -l postgres -c '/usr/bin/postmaster -S -D/var/lib/pgsql'

So all you'll have to do is change it as it appears above with
the -i switch (and I also recommend the -o -F pair as well). 

Hope that helps,

Mike Mascari

P.S.: If you are using the older RPMS with an older version of
PostgreSQL (6.x), I highly recommend upgrading. Major bugs fixes
and enhancements were made between the 6.x series and 7.x.

Good Luck!



^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 05:53  Oliver Elphick <olly@lfix.co.uk>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  2 siblings, 1 reply; 18+ messages in thread

From: Oliver Elphick @ 2000-07-31 05:53 UTC (permalink / raw)
  To: pgsql-interfaces

Tom Lane wrote:
  >"David Lloyd-Jones" <david.lloyd-jones@attcanada.ca> writes:
  >> than one can read them) but I don't see how this adds up: I'm not on a
  >> network, and PSQL, which is a front end to PostgreSQL, just like PGAccess 
      >is
  >> supposed to be, is running fine.
  >
  >By default, psql connects via a Unix-socket path, not by TCP.  PGAccess
  >is written differently and always tries to connect by TCP.  If you try
  >to start psql with "-h localhost" or some such, it will try TCP and
  >fail in the same way ...

If you leave blank the host field of pgaccess's connection dialog, it will
use UNIX sockets instead of TCP/IP.

-- 
Oliver Elphick                                Oliver.Elphick@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47  6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
                 ========================================
     "Have not I commanded thee? Be strong and of a good 
      courage; be not afraid, neither be thou dismayed; for 
      the LORD thy God is with thee whithersoever thou 
      goest."                        Joshua 1:9 





^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 05:54  Constantin Teodorescu <teo@flex.ro>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  2 siblings, 0 replies; 18+ messages in thread

From: Constantin Teodorescu @ 2000-07-31 05:54 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; pgsql-interfaces

Tom Lane wrote:
> 
> "David Lloyd-Jones" <david.lloyd-jones@attcanada.ca> writes:
> > than one can read them) but I don't see how this adds up: I'm not on a
> > network, and PSQL, which is a front end to PostgreSQL, just like PGAccess is
> > supposed to be, is running fine.
> 
> By default, psql connects via a Unix-socket path, not by TCP.  PGAccess
> is written differently and always tries to connect by TCP.  If you try
> to start psql with "-h localhost" or some such, it will try TCP and
> fail in the same way ...

BTW, is there a way to connect to PostgreSQL with libpgtcl with
Unix-socket?
Any parameters? In that case I can try changing PgAccess to connect in
both ways!

-- 
Constantin Teodorescu
General Investment Group
Braila, ROMANIA



^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 06:28  David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  parent: Oliver Elphick <olly@lfix.co.uk>
  0 siblings, 1 reply; 18+ messages in thread

From: David Lloyd-Jones @ 2000-07-31 06:28 UTC (permalink / raw)
  To: pgsql-interfaces; Oliver Elphick <olly@lfix.co.uk>

Oliver:

                Bingo!

                                 Gratefully,


                                                 -dlj.


PS: More generally, I'd still like to know what to do with the script
"postgresql start" which is in subdirectory /etc/rc.d/init.d/  of RH 6.2.
There are lines that look somewhat like Mike Mascari's suggestions, but
nothing right on.  Lamar Owen, are you out there somewhere?

                                                    -d.




----- Original Message -----
From: "Oliver Elphick" <olly@lfix.co.uk>
To: <pgsql-interfaces@postgresql.org>
Sent: Monday, July 31, 2000 1:53 AM
Subject: Re: [INTERFACES] PSQL Working, but PGAccess Not Connecting.


> Tom Lane wrote:
>   >"David Lloyd-Jones" <david.lloyd-jones@attcanada.ca> writes:
>   >> than one can read them) but I don't see how this adds up: I'm not on
a
>   >> network, and PSQL, which is a front end to PostgreSQL, just like
PGAccess
>       >is
>   >> supposed to be, is running fine.
>   >
>   >By default, psql connects via a Unix-socket path, not by TCP.  PGAccess
>   >is written differently and always tries to connect by TCP.  If you try
>   >to start psql with "-h localhost" or some such, it will try TCP and
>   >fail in the same way ...
>
> If you leave blank the host field of pgaccess's connection dialog, it will
> use UNIX sockets instead of TCP/IP.
>
> --
> Oliver Elphick                                Oliver.Elphick@lfix.co.uk
> Isle of Wight                              http://www.lfix.co.uk/oliver
> PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47  6B 7E 39 CC 56 E4 C1 47
> GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
>                  ========================================
>      "Have not I commanded thee? Be strong and of a good
>       courage; be not afraid, neither be thou dismayed; for
>       the LORD thy God is with thee whithersoever thou
>       goest."                        Joshua 1:9
>
>
>




^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 14:58  Thomas Lockhart <lockhart@alumni.caltech.edu>
  parent: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  0 siblings, 1 reply; 18+ messages in thread

From: Thomas Lockhart @ 2000-07-31 14:58 UTC (permalink / raw)
  To: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; +Cc: pgsql-interfaces@postgresql.org, Oliver Elphick <olly@lfix.co.uk>

> PS: More generally, I'd still like to know what to do with the script
> "postgresql start" which is in subdirectory /etc/rc.d/init.d/  of RH 6.2.
> There are lines that look somewhat like Mike Mascari's suggestions, but
> nothing right on.  Lamar Owen, are you out there somewhere?

That is intended to start up and shut down the Postgres server when your
system boot or halts. It needs a soft link in /etc/rc.d/rc3.d and /rc5.d
to actually get invoked automatically. I usually set it up as a "S99"
script, but Lamar may have a different convention for his RPMs.

What else do you need to know about it?

                   - Thomas



^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 16:24  David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
  0 siblings, 1 reply; 18+ messages in thread

From: David Lloyd-Jones @ 2000-07-31 16:24 UTC (permalink / raw)
  To: Thomas Lockhart <lockhart@alumni.caltech.edu>; David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; +Cc: pgsql-interfaces; Oliver Elphick <olly@lfix.co.uk>


----- Original Message -----
From: "Thomas Lockhart" <lockhart@alumni.caltech.edu>
To: "David Lloyd-Jones" <david.lloyd-jones@attcanada.ca>
Cc: <pgsql-interfaces@postgresql.org>; "Oliver Elphick" <olly@lfix.co.uk>
Sent: Monday, July 31, 2000 10:58 AM
Subject: Re: [INTERFACES] PSQL Working, but PGAccess Not Connecting.


> > PS: More generally, I'd still like to know what to do with the script
> > "postgresql start" which is in subdirectory /etc/rc.d/init.d/  of RH
6.2.
> > There are lines that look somewhat like Mike Mascari's suggestions, but
> > nothing right on.  Lamar Owen, are you out there somewhere?
>
> That is intended to start up and shut down the Postgres server when your
> system boot or halts. It needs a soft link in /etc/rc.d/rc3.d and /rc5.d
> to actually get invoked automatically. I usually set it up as a "S99"
> script, but Lamar may have a different convention for his RPMs.
>
> What else do you need to know about it?
>

Tom,

Do I want to add a "-i" somewhere inside it?

Or is there some other way of making the postmaster talk to "the network"?
If so, what would the command line be?

                                           Many thanks,

                                                        -dlj.






^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 16:32  Thomas Lockhart <lockhart@alumni.caltech.edu>
  parent: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  0 siblings, 2 replies; 18+ messages in thread

From: Thomas Lockhart @ 2000-07-31 16:32 UTC (permalink / raw)
  To: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; +Cc: pgsql-interfaces@postgresql.org, Oliver Elphick <olly@lfix.co.uk>

> Do I want to add a "-i" somewhere inside it?

Sure, if it isn't there already. I haven't looked at the script
recently, but I recall that the predecessor had some commented-out lines
to illustrate where this kind of thing should occur.

Perhaps the "-i" is disabled by default to enhance out-of-the-box
network security?

                       - Thomas



^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-07-31 18:54  Lamar Owen <lamar.owen@wgcr.org>
  parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
  1 sibling, 1 reply; 18+ messages in thread

From: Lamar Owen @ 2000-07-31 18:54 UTC (permalink / raw)
  To: Thomas Lockhart <lockhart@alumni.caltech.edu>; +Cc: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; pgsql-interfaces@postgresql.org, Oliver Elphick <olly@lfix.co.uk>

Thomas Lockhart wrote:
 
> > Do I want to add a "-i" somewhere inside it?
 
> Sure, if it isn't there already. I haven't looked at the script
> recently, but I recall that the predecessor had some commented-out lines
> to illustrate where this kind of thing should occur.
 
> Perhaps the "-i" is disabled by default to enhance out-of-the-box
> network security?

[I'm going to reply to this one rather than all the previous ones. 
Sorry for the delay in responding, but I just got back from a 'working'
vacation, and had alot of front-burner items to handle before I could
get on my notebook. And, last night I was going to get online, but a
thunderstorm outbreak prevented me....]

David, if you're running 6.5.3 that came with RH 6.2, there should
already be a '-i' on the postmaster startup line in
/etc/rc.d/init.d/postgresql.  If, however, you're running 7.0.2, the
whole startup has changed.  Look in
/var/lib/pgsql/data/postmaster.opts.default (IIRC) for a '-i' -- the
7.0.2 RPM's start postmaster through pgctl.

If you not running 7.0.2, you really should investigate upgrading. 
AOLserver's performance takes a leap against 7 versus 6.5, for some
reason that I've not been able to fathom.

As to the network unreachable errors, you have a network configuration
problem somewhere that is causing your machine to not work with TCP/IP,
for some reason.  

The default startup in the RPM's has been, since 6.5.2 or so, to enable
the -i -- and the reason -i wasn't enabled before wasn't so much
security as it was the fact the no one bothered to add -i to the startup
file after PostgreSQL 6.3 changed the default to require -i for TCP/IP
connections.

Also, if you have Apache installed, AOLserver will have serious trouble
binding port 80 (even if Apache is not running).

HTH

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11



^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: PSQL Working, but PGAccess Not Connecting.
@ 2000-08-02 00:42  David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
  parent: Lamar Owen <lamar.owen@wgcr.org>
  0 siblings, 0 replies; 18+ messages in thread

From: David Lloyd-Jones @ 2000-08-02 00:42 UTC (permalink / raw)
  To: Lamar Owen <lamar.owen@wgcr.org>; Thomas Lockhart <lockhart@alumni.caltech.edu>; +Cc: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>; pgsql-interfaces; Oliver Elphick <olly@lfix.co.uk>


"Lamar Owen" <lamar.owen@wgcr.org> wrote:
>
> [I'm going to reply to this one ....]
>
> David, if you're running 6.5.3 that came with RH 6.2, there should
> already be a '-i' on the postmaster startup line in
> /etc/rc.d/init.d/postgresql.  If, however, you're running 7.0.2, the
> whole startup has changed.  Look in
> /var/lib/pgsql/data/postmaster.opts.default (IIRC) for a '-i' -- the
> 7.0.2 RPM's start postmaster through pgctl.

Lamar,

Many thanks. Yep, the -i is there as you say, and yes, 7.0.2 is what I'm
running.

So the quewstion becomes, How do I go looking for other causes?

And incidentally, how do I get rid of Apache to avoid the interfrence
problem on port 80 that you mention?

In case Lamar doesn't get this for a day or so, replies off-line from the
other people on the list will be welcome.

                                        Cheers,

                                                 -dlj.






^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: [INTERFACES] PSQL Working, but PGAccess Not Connecting.
@ 2000-08-16 23:28  tuan <nguyen_a@cnam.fr>
  parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
  1 sibling, 1 reply; 18+ messages in thread

From: tuan @ 2000-08-16 23:28 UTC (permalink / raw)
  To: pgsql-novice@postgresql.org <pgsql-novice@postgresql.org>

Thomas Lockhart wrote:
> 
> 
> Perhaps the "-i" is disabled by default to enhance out-of-the-box
> network security?
> 
>                        - Thomas
Hi,

Could you tell why it is less secure to run postmaster in IP sockets
than using Unix sockets ?

TIA

PS: I am awaiting for the final release of Postgres' book  , as a not-e.professional
working in a not-dot.industry I still prefer a book's touch over a monitor's glare ...

-- 
     /\   /\
    (  '''  )
    _(O)-(O)_ 
   (,,) Y (,,)
   ===\[_]/===
    ¤-((_))-¤




^ permalink  raw  reply  [nested|flat] 18+ messages in thread

* Re: Re: [INTERFACES] PSQL Working, but PGAccess Not Connecting.
@ 2000-08-17 02:04  ghaverla@freenet.edmonton.ab.ca
  parent: tuan <nguyen_a@cnam.fr>
  0 siblings, 0 replies; 18+ messages in thread

From: ghaverla@freenet.edmonton.ab.ca @ 2000-08-17 02:04 UTC (permalink / raw)
  To: tuan <nguyen_a@cnam.fr>; +Cc: pgsql-novice@postgresql.org <pgsql-novice@postgresql.org>


On Thu, 17 Aug 2000, tuan wrote:
> Thomas Lockhart wrote:

> > Perhaps the "-i" is disabled by default to enhance out-of-the-box
> > network security?

> Could you tell why it is less secure to run postmaster in IP sockets
> than using Unix sockets ?

I'll take a stab at this.  Unix sockets are confined to the
single machine in question.  IP Sockets are (potentially)
open to the network.  Larger population of intruders.

Gord

Matter Realisations     http://www.materialisations.com/
Gordon Haverland, B.Sc. M.Eng. President
101  9504 182 St. NW    Edmonton, AB, CA  T5T 3A7
780/481-8019            ghaverla @ freenet.edmonton.ab.ca




^ permalink  raw  reply  [nested|flat] 18+ messages in thread


end of thread, other threads:[~2000-08-17 02:04 UTC | newest]

Thread overview: 18+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-07-30 19:23 Re: PSQL Working, but PGAccess Not Connecting. David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
2000-07-30 21:40 ` Tom Lane <tgl@sss.pgh.pa.us>
2000-07-30 22:21   ` David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
2000-07-30 22:34     ` Tom Lane <tgl@sss.pgh.pa.us>
2000-07-31 01:54       ` Red Pineseed <yue207@home.com>
2000-07-31 03:42         ` Mike Mascari <mascarm@mascari.com>
2000-07-31 04:17         ` David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
2000-07-31 04:53           ` Mike Mascari <mascarm@mascari.com>
2000-07-31 05:53       ` Oliver Elphick <olly@lfix.co.uk>
2000-07-31 06:28         ` David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
2000-07-31 14:58           ` Thomas Lockhart <lockhart@alumni.caltech.edu>
2000-07-31 16:24             ` David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
2000-07-31 16:32               ` Thomas Lockhart <lockhart@alumni.caltech.edu>
2000-07-31 18:54                 ` Lamar Owen <lamar.owen@wgcr.org>
2000-08-02 00:42                   ` David Lloyd-Jones <david.lloyd-jones@attcanada.ca>
2000-08-16 23:28                 ` tuan <nguyen_a@cnam.fr>
2000-08-17 02:04                   ` ghaverla@freenet.edmonton.ab.ca
2000-07-31 05:54       ` Constantin Teodorescu <teo@flex.ro>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox