There are no firewalling issues, routing or dns issues. Basically nothing has changed with the server. The only change is with the clients that connect. Everything seems to work fine connecting from the local socket but when you try to connect over tcp, it doesn't work because it is not listening on the port. For some reason, I cannot get it to listen on the port unless I specify in my postmaster command -h ip.address. I am using postgres 7.3.2 on redhat 7.1 on the server. On the clients, it is RH9.0 with the same postgres version installed from a tarball. I bet if I reboot the machine, everything will work but I don't want to lose my uptime:-) -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Thursday, April 29, 2004 9:35 PM To: Richard Gass Cc: 'pgsql-general@postgresql.org' Subject: Re: TCP only listening on localhost??? Richard Gass <rgass@sprintlabs.com> writes: > This was all working fine until I recently. It has been a long time > since I have restarted the server ( 5:05pm up 377 days, 18:36, 7 > users, load > average: 0.00, 0.00, 0.00) and it has been a long time since I restarted the > postgres DB. I wonder if some weirdness is happening which isn't allowing > postgres to bind to tcp port 5432. This seems really really odd. Have you touched the machine's firewall configuration (iptables or whatever) lately? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
