pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: gilberto.castillo@etecsa.cu
To: soumik.bhattacharjee@kpn.com
Cc: pgsql-admin@lists.postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: [MASSMAIL]Cannot connect to postgresql on port 5432
Date: Mon, 23 Dec 2019 14:34:11 -0500
Message-ID: <3992c5f7d10f011266aeaeb55563920c@etecsa.cu> (raw)
In-Reply-To: <2A91BEF8171A5349931391E0C721CC537D772EF8@CPEMS-KPN501.KPNCNL.LOCAL>
References: <2A91BEF8171A5349931391E0C721CC537D772EF8@CPEMS-KPN501.KPNCNL.LOCAL>

Hi

You might change postgresl.conf the line listening = '*'

El 2019-12-23 14:30, soumik.bhattacharjee@kpn.com escribió:
> Hi Experts,
> 
> Post installation of  PostgreSQL it is not listening on an IP, only on
> localhost.
> 
> Please suggest your inputs.
> 
> USED BELOW COMMAND FOR INSTALLATIONS –
> 
> # APT-GET INSTALL POSTGRESQL-12
> 
> postgres=# select version();
> 
>                                                      version
> 
> ------------------------------------------------------------------------------------------------------------------
> 
> 
> PostgreSQL 12.1 (Debian 12.1-1.pgdg100+1) on x86_64-pc-linux-gnu,
> compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
> 
> (1 row)
> 
> ENTRIES IN ::: /ETC/POSTGRESQL/12/MAIN/PG_HBA.CONF
> 
> # Database administrative login by Unix domain socket
> 
> local   all             postgres                                peer
> 
> # TYPE  DATABASE        USER            ADDRESS                 METHOD
> 
> 
> # "local" is for Unix domain socket connections only
> 
> local   all             all                                     peer
> 
> # IPv4 local connections:
> 
> host    all             all             127.0.0.1/32            md5
> 
> # IPv6 local connections:
> 
> host    all             all             ::1/128                 md5
> 
> # Allow replication connections from localhost, by a user with the
> 
> # replication privilege.
> 
> local   replication     all                                     peer
> 
> host    replication     all             127.0.0.1/32            md5
> 
> host    replication     all             ::1/128                 md5
> 
> NOT CONNECTED
> 
> POSTGRES@SRV:/OPT$ NETSTAT -NLP | GREP 5432
> 
> (Not all processes could be identified, non-owned process info
> 
> will not be shown, you would have to be root to see it all.)
> 
> tcp        0      0 127.0.0.1:5432          0.0.0.0:*
> LISTEN      25857/postgres
> 
> unix  2      [ ACC ]     STREAM     LISTENING     74234
> 25857/postgres       /var/run/postgresql/.s.PGSQL.5432
> 
> POSTGRES@SRV:~$ TELNET 10.133.214.32 5432
> 
> Trying 10.133.214.32...
> 
> telnet: Unable to connect to remote host: Connection refused





view thread (8+ messages)  latest in thread

Message-ID: <3992c5f7d10f011266aeaeb55563920c@etecsa.cu>
Permalink:  ../3992c5f7d10f011266aeaeb55563920c@etecsa.cu/
Also on:    postgresql.org/message-id/3992c5f7d10f011266aeaeb55563920c@etecsa.cu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: gilberto.castillo@etecsa.cu, soumik.bhattacharjee@kpn.com, pgsql-admin@lists.postgresql.org
  Subject: Re: [MASSMAIL]Cannot connect to postgresql on port 5432
  In-Reply-To: <3992c5f7d10f011266aeaeb55563920c@etecsa.cu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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