Обсуждение: RedHat 5.1 Postgres 6.3.2 problem resolved

Поиск
Список
Период
Сортировка

RedHat 5.1 Postgres 6.3.2 problem resolved

От
De Clarke
Дата:
The default RedHat install doesn't include pidentd, which
apparently is now required by PG (?).  When I install the
RPM for pidentd, I get past the "unrecognized authentication"
problem.


But I still have a configuration problem of some kind:
I cannot connect to the postmaster.


86) musashi.ucolick.org.postgres: psql -d template1
Connection to database 'template1' failed.
connectDB() failed: Is the postmaster running and accepting TCP/IP(with -i) connections at 'localhost' on port '5432'?


87) musashi.ucolick.org.postgres: telnet localhost 5432
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
88) musashi.ucolick.org.postgres:


I can connect to other services on localhost (the usual inetd stuff).

This feels like a slight Linux misconfig problem.... has anyone else
been here?

de


Re: [HACKERS] RedHat 5.1 Postgres 6.3.2 problem resolved

От
The Hermit Hacker
Дата:
On Thu, 18 Jun 1998, De Clarke wrote:

>
> The default RedHat install doesn't include pidentd, which
> apparently is now required by PG (?).  When I install the
> RPM for pidentd, I get past the "unrecognized authentication"
> problem.

check the pg_hba.conf file...ident authentication is an option but it
isn't "shipped" by us with it enabled...

> 86) musashi.ucolick.org.postgres: psql -d template1
> Connection to database 'template1' failed.
> connectDB() failed: Is the postmaster running and accepting TCP/IP(with -i) connections at 'localhost' on port
'5432'?

This one sounds like you have PGHOST set to a value, so its trying to use
a TCP/IP vs Unix Domain Socket for the connection.  Either restart
postmaster with the -i option, or set PGHOST to NULL (environment
variable)

> 87) musashi.ucolick.org.postgres: telnet localhost 5432
> Trying 127.0.0.1...
> telnet: Unable to connect to remote host: Connection refused
> 88) musashi.ucolick.org.postgres:

    Same as above...without the -i option, it doesn't listen on port
5432...