Thread: BUG #10917: How to connect pgadmin of another system.

BUG #10917: How to connect pgadmin of another system.

From
emonrockz143@gmail.com
Date:
The following bug has been logged on the website:

Bug reference:      10917
Logged by:          Emon
Email address:      emonrockz143@gmail.com
PostgreSQL version: 9.1.0
Operating system:   Ubuntu 12.04
Description:

Hi,

I have pgAdmin in two systems with the IPs 192.168.1.1 and 192.168.1.2. , I
want to add the server 192.168.1.2 in PgAdmin of 192.168.1.1 sytem. I am
getting the following error.

could not connect to server: Connection refused Is the server running on
host "192.168.1.2" and accepting TCP/IP connections on port 5432?

Following is my pg_hba.conf file

# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the "Client Authentication" section in the PostgreSQL
# documentation for a complete description of this file.  A short
# synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access.  Records take one of these forms:
#
# local      DATABASE  USER  METHOD  [OPTIONS]
# host       DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
# hostssl    DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
# hostnossl  DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain
# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
# plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samerole", "replication", a
# database name, or a comma-separated list thereof. The "all"
# keyword does not match "replication". Access to replication
# must be enabled in a separate record (see example below).
#
# USER can be "all", a user name, a group name prefixed with "+", or a
# comma-separated list thereof.  In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names
# from a separate file.
#
# ADDRESS specifies the set of hosts the record matches.  It can be a
# host name, or it is made up of an IP address and a CIDR mask that is
# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
# specifies the number of significant bits in the mask.  A host name
# that starts with a dot (.) matches a suffix of the actual host name.
# Alternatively, you can write an IP address and netmask in separate
# columns to specify the set of hosts.  Instead of a CIDR-address, you
# can write "samehost" to match any of the server's own IP addresses,
# or "samenet" to match any address in any subnet that the server is
# directly connected to.
#
# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
# "krb5", "ident", "peer", "pam", "ldap", "radius" or "cert".  Note that
# "password" sends passwords in clear text; "md5" is preferred since
# it sends encrypted passwords.
#
# OPTIONS are a set of options for the authentication in the format
# NAME=VALUE.  The available options depend on the different
# authentication methods -- refer to the "Client Authentication"
# section in the documentation for a list of which options are
# available for which authentication methods.
#
# Database and user names containing spaces, commas, quotes and other
# special characters must be quoted.  Quoting one of the keywords
# "all", "sameuser", "samerole" or "replication" makes the name lose
# its special character, and just match a database or username with
# that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal.  If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect.  You can
# use "pg_ctl reload" to do that.

# Put your actual configuration here
# ----------------------------------
#
# If you want to allow non-local connections, you need to add more
# "host" records.  In that case you will also need to make PostgreSQL
# listen on a non-local interface via the listen_addresses
# configuration parameter, or via the -i or -h command line switches.

# DO NOT DISABLE!

# If you change this first entry you will need to make sure that the
# database superuser can access the database using some other method.
# Noninteractive access to all databases is required during automatic
# maintenance (custom daily cronjobs, replication, and similar tasks).
#
# Database administrative login by Unix domain socket
local   all             postgres                                md5

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     trust
# 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     postgres                                trust
#host    replication     postgres        127.0.0.1/32            md5
#host    replication     postgres        ::1/128                 md5

Please help me with a solution so that I can add 192.168.1.2 as a pgadmin
server in 192.168.1.1. Thank you in advance.



Regards,

Emon.

Re: BUG #10917: How to connect pgadmin of another system.

From
Francisco Olarte
Date:
Hi:

On Thu, Jul 10, 2014 at 4:34 PM,  <emonrockz143@gmail.com> wrote:
...
> I have pgAdmin in two systems with the IPs 192.168.1.1 and 192.168.1.2. , I
> want to add the server 192.168.1.2 in PgAdmin of 192.168.1.1 sytem. I am
> getting the following error.
>
> could not connect to server: Connection refused Is the server running on
> host "192.168.1.2" and accepting TCP/IP connections on port 5432?

Seems pilot error, not a bug. Have checked that?

Also:

> # IPv4 local connections:
> host    all             all             127.0.0.1/32            md5
> # IPv6 local connections:
> host    all             all             ::1/128                 md5
>
> Please help me with a solution so that I can add 192.168.1.2 as a pgadmin
> server in 192.168.1.1. Thank you in advance.

You have only LOCAL ip connections allowed, try allowing remote from
192.168.1.1 in 1.2 and, check you are allowing tcp connections in
postgresql.conf.

Try sending to the psql-general list if you have problems to do it, as
this seems not to be a bug and is easier to get it answered there. I'd
also recommend to read the docs a bit more.

Francisco Olarte.

Re: BUG #10917: How to connect pgadmin of another system.

From
David G Johnston
Date:
emonrockz143 wrote
> Please help me with a solution so that I can add 192.168.1.2 as a pgadmin
> server in 192.168.1.1. Thank you in advance.

I am assuming you haven't read or understood the documentation for
pg_hba.conf

http://www.postgresql.org/docs/9.3/interactive/auth-pg-hba-conf.html

It is also excessive to copy the entire standard boiler-plate comments in
you file - the uncommented lines would have been sufficient.

As noted this is not a bug and thus this is not the proper forum for such
help.  I suggest reading the above link thoroughly and probably multiple
times, adjusting your pg_hba.conf and postgres.conf files as you go, then
re-post to -general if you haven't figured it out.

Once the server is capable of allow remote clients to connect to it
configuring pgAdmin is quite simple.  i.e., pgAdmin is not the problem here
but rather the remote server configuration (postgres and possibly OS stuff
like firewalls).

You will probably find it easier to use "psql" instead of pgAdmin to do the
trial-and-error configuration process - and it will remove one extra layer
of indirection from the equation as well.

David J.




--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-10917-How-to-connect-pgadmin-of-another-system-tp5811145p5811151.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.