Thread: Attempting to connect
Hi I do need some help here. I am still having trouble making a remote connection. The 'Server doesn't listen' message comes up. The config files have been changed as shown below. Postgresql.conf #listen_addresses = '*' pg_hba # TYPE DATABASE USER CIDR-ADDRESs IP-Mask METHOD # IPv4 local connections: host all all 0.0.0.0 255.255.255.255 md5 host all all 127.0.0.1/32 md5 # IPv6 local connections: host all all ::1/128 md5 I disconnect the firewall during the connection attempt. After changes to the above file I run - pg_ctl reload - and stop/start the server. The last few log entries follows. 2009-02-15 13:01:54 PST LOG: loaded library "$libdir/plugins/plugin_debugger.dll" 2009-02-15 13:02:10 PST LOG: loaded library "$libdir/plugins/plugin_debugger.dll" 2009-02-15 13:10:39 PST LOG: loaded library "$libdir/plugins/plugin_debugger.dll" 2009-02-15 13:16:16 PST LOG: received SIGHUP, reloading configuration files 2009-02-15 13:16:52 PST LOG: loaded library "$libdir/plugins/plugin_debugger.dll" The latest couple of attempts didn't leave a log behind. Thanks Bob
Bob Pawley wrote: > Hi > > I do need some help here. > > I am still having trouble making a remote connection. The 'Server > doesn't listen' message comes up. > > The config files have been changed as shown below. > > Postgresql.conf > > #listen_addresses = '*' you'd need to remove that # (comment) from the front if you want it to pay attention....
Removed # Reloaded postmaster, restarted server. Server still isn't listening. Bob ----- Original Message ----- From: "John R Pierce" <pierce@hogranch.com> To: "Bob Pawley" <rjpawley@shaw.ca>; <pgsql-general@postgresql.org> Sent: Sunday, February 15, 2009 1:44 PM Subject: Re: [GENERAL] Attempting to connect > Bob Pawley wrote: >> Hi >> >> I do need some help here. >> >> I am still having trouble making a remote connection. The 'Server >> doesn't listen' message comes up. >> >> The config files have been changed as shown below. >> >> Postgresql.conf >> >> #listen_addresses = '*' > > > you'd need to remove that # (comment) from the front if you want it to > pay attention.... > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general
On Sunday 15 February 2009 1:41:14 pm Bob Pawley wrote: > Hi > > I do need some help here. > > I am still having trouble making a remote connection. The 'Server doesn't > listen' message comes up. > > The config files have been changed as shown below. > > Postgresql.conf > > #listen_addresses = '*' > > pg_hba > > # TYPE DATABASE USER CIDR-ADDRESs IP-Mask METHOD > > # IPv4 local connections: > host all all 0.0.0.0 > 255.255.255.255 md5 > host all all 127.0.0.1/32 > md5 > # IPv6 local connections: > host all all ::1/128 > md5 > > I disconnect the firewall during the connection attempt. > > After changes to the above file I run - pg_ctl reload - and stop/start the > server. > > The last few log entries follows. > > 2009-02-15 13:01:54 PST LOG: loaded library > "$libdir/plugins/plugin_debugger.dll" > 2009-02-15 13:02:10 PST LOG: loaded library > "$libdir/plugins/plugin_debugger.dll" > 2009-02-15 13:10:39 PST LOG: loaded library > "$libdir/plugins/plugin_debugger.dll" > 2009-02-15 13:16:16 PST LOG: received SIGHUP, reloading configuration > files 2009-02-15 13:16:52 PST LOG: loaded library > "$libdir/plugins/plugin_debugger.dll" > > The latest couple of attempts didn't leave a log behind. > > Thanks > > Bob The server is running? Can you connect locally? I don't know how you have logging setup, but when I stop/start a server it generates a new log file. Are you sure you are looking at the most recent log? -- Adrian Klaver aklaver@comcast.net
The log file states "parameter "listen-adress" cannot be changed after server start; conf change ignored. I am getting this log entry after saving the file and reloading with the server shutdown. Does anyone have a procedure for making changes to this file? Bob ----- Original Message ----- From: "John R Pierce" <pierce@hogranch.com> To: "Bob Pawley" <rjpawley@shaw.ca>; <pgsql-general@postgresql.org> Sent: Sunday, February 15, 2009 1:44 PM Subject: Re: [GENERAL] Attempting to connect > Bob Pawley wrote: >> Hi >> >> I do need some help here. >> >> I am still having trouble making a remote connection. The 'Server doesn't >> listen' message comes up. >> >> The config files have been changed as shown below. >> >> Postgresql.conf >> >> #listen_addresses = '*' > > > you'd need to remove that # (comment) from the front if you want it to pay > attention.... > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general
On Sunday 15 February 2009 2:19:13 pm Adrian Klaver wrote: > On Sunday 15 February 2009 1:41:14 pm Bob Pawley wrote: > > Hi > > > > I do need some help here. > > > > I am still having trouble making a remote connection. The 'Server doesn't > > listen' message comes up. > > > > The config files have been changed as shown below. > > > > Postgresql.conf > > > > #listen_addresses = '*' > > > > pg_hba > > > > # TYPE DATABASE USER CIDR-ADDRESs IP-Mask METHOD > > > > # IPv4 local connections: > > host all all 0.0.0.0 > > 255.255.255.255 md5 > > host all all 127.0.0.1/32 > > md5 > > # IPv6 local connections: > > host all all ::1/128 > > md5 > > > > I disconnect the firewall during the connection attempt. > > > > After changes to the above file I run - pg_ctl reload - and stop/start > > the server. > > > > The last few log entries follows. > > > > 2009-02-15 13:01:54 PST LOG: loaded library > > "$libdir/plugins/plugin_debugger.dll" > > 2009-02-15 13:02:10 PST LOG: loaded library > > "$libdir/plugins/plugin_debugger.dll" > > 2009-02-15 13:10:39 PST LOG: loaded library > > "$libdir/plugins/plugin_debugger.dll" > > 2009-02-15 13:16:16 PST LOG: received SIGHUP, reloading configuration > > files 2009-02-15 13:16:52 PST LOG: loaded library > > "$libdir/plugins/plugin_debugger.dll" > > > > The latest couple of attempts didn't leave a log behind. > > > > Thanks > > > > Bob > > The server is running? Can you connect locally? I don't know how you have > logging setup, but when I stop/start a server it generates a new log file. > Are you sure you are looking at the most recent log? > > -- > Adrian Klaver > aklaver@comcast.net Just saw this: host all all 0.0.0.0 255.255.255.255 md5 You should change this to 0.0.0.0/0 and ditch the the netmask. See examples at bottom of page below for more information- http://www.postgresql.org/docs/8.3/interactive/auth-pg-hba-conf.html -- Adrian Klaver aklaver@comcast.net
On Sun, Feb 15, 2009 at 3:29 PM, Bob Pawley <rjpawley@shaw.ca> wrote: > The log file states "parameter "listen-adress" cannot be changed after > server start; conf change ignored. > > I am getting this log entry after saving the file and reloading with the > server shutdown. > > Does anyone have a procedure for making changes to this file? You need to restart, not reload, the database server.
> # IPv4 local connections: > host all all 0.0.0.0 > 255.255.255.255 md5 > host all all 127.0.0.1/32 md5 oh. that first HOST line will only allow IP 0.0.0.0, hardly likely to be a valid address. if you want to allow connections from ALL IPs, use 0.0.0.0/0 or 0.0.0.0 0.0.0.0 the second line allows connections to localhost only.
Finally Success Thanks everyone Bob ----- Original Message ----- From: "John R Pierce" <pierce@hogranch.com> To: "Bob Pawley" <rjpawley@shaw.ca> Cc: "PostgreSQL" <pgsql-general@postgresql.org> Sent: Sunday, February 15, 2009 3:05 PM Subject: Re: [GENERAL] Attempting to connect > >> # IPv4 local connections: >> host all all 0.0.0.0 >> 255.255.255.255 md5 >> host all all 127.0.0.1/32 md5 > > > > oh. that first HOST line will only allow IP 0.0.0.0, hardly likely to > be a valid address. if you want to allow connections from ALL IPs, use > 0.0.0.0/0 or 0.0.0.0 0.0.0.0 > > the second line allows connections to localhost only. > > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general
Woohoo! Glad you got it working...
At 3:34 PM -0800 2/15/09, Bob Pawley wrote: >Finally Success > >Thanks everyone > Here's one I ran into today - connection with the server was blocked by Kasperski Anti-Virus. The clue was that other machines on the network could connect, but this one couldn't. Funny thing was that we had originally had it connecting, then then next day it wouldn't (anti-virus update maybe). But people should add this to their toolkit when they're looking for connection problems. -Owen