Re: weird network issue - Mailing list pgsql-admin
From | kevin kempter |
---|---|
Subject | Re: weird network issue |
Date | |
Msg-id | CE2ED85C-3B18-4F0E-A66F-9E174E1D86E9@kevinkempterllc.com Whole thread Raw |
In response to | weird network issue (kevin kempter <kevin@kevinkempterllc.com>) |
Responses |
Re: weird network issue
|
List | pgsql-admin |
Not sure. I'm not so well versed in the firewall/networking areas. I can however do an scp pull from both machines : scp a file from 192.168.111.13 while logged onto 192.168.111.11 and scp a file from 192.168.111.11 while logged onto 192.168.111.13 Can you point me where to look for firewall/iptables/SE issues? Thanks in advance On Mar 28, 2008, at 10:45 AM, Jonathan Nalley wrote: > are you running any kind of firewall/iptables/SELinux where the > settings are perhaps not the same on the two machines? > > > From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org > ] On Behalf Of kevin kempter > Sent: Friday, March 28, 2008 12:31 > To: pgsql-admin@postgresql.org > Subject: [ADMIN] weird network issue > > Hi LIst; > > I have 2 Linux servers: > 192.168.111.11 > 192.168.111.13 > > Both are running postgres v 8.2.6 > > I can ping the .11 box from .13 and vice versa > I can connect remotely from the .11 box to the .13 box but I cannot > connect to the .11 box from the .13 box. > > I can do this: > > on the 192.168.111.11 box: > > -bash-3.1$ psql -h 192.168.111.13 > Welcome to psql 8.2.6, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > postgres=# > > However if I do this it fails: > > on the 192.168.111.13 box: > > -bash-3.1$ psql -h 192.168.111.11 postgres > psql: could not connect to server: No route to host > Is the server running on host "192.168.111.11" and accepting > TCP/IP connections on port 5432? > > > > Both boxes have the same copy of the postgresql.conf file and the > pg_hba.conf file. > > Here's the listen address setting (on the 192.168.111.11 box) from > the postgresql.conf file: > listen_addresses = '*' > > > I also checked (after a restart) that the listen address and port > was in fact as I thought > on 192.168.111.11 : > > > Welcome to psql 8.2.6, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > postgres=# show listen_addresses; > listen_addresses > ------------------ > * > (1 row) > > postgres=# show port > ; > port > ------ > 5432 > (1 row) > > postgres=# > > > Here's the current pg_hba.conf file on 192.168.111.11 : > > > > # TYPE DATABASE USER CIDR-ADDRESS METHOD > > # "local" is for Unix domain socket connections only > local all all ident sameuser > # IPv4 local connections: > host all all 127.0.0.1/32 ident sameuser > # IPv6 local connections: > host all all ::1/128 ident sameuser > > #DRW. This should be tighted up once the db instances are figured out > host all all 192.168.111.0/24 trust > > > > I'm stumped.. > > Anyone have any thoughts ? > > Thanks in advance. > >
pgsql-admin by date: