could not create socket for statistics collector: Protocol not supported

Started by Chris Ochsover 21 years ago3 messagesgeneral
Jump to latest
#1Chris Ochs
chris@paymentonline.com

I'm a little confused about why I am getting this. I was reading a message
from Tom earlier that said it was because postgresql could not bind to
localhost, but the statistics collector is running and localhost does
resolve to 127.0.0.1. There is no dns server, only an /etc/hosts file. Is
it possible that it's still resolving fine, but either getaddrinfo() or
something else is returning an error because there is no dns server
available? I do see a lot of failed connection attempts to port 53 from
postgres. This is on freebsd 5.2.1/Posgresql beta1.

Chris

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Chris Ochs (#1)
Re: could not create socket for statistics collector: Protocol not supported

"Chris" <chris@paymentonline.com> writes:

I'm a little confused about why I am getting this. I was reading a message
from Tom earlier that said it was because postgresql could not bind to
localhost, but the statistics collector is running and localhost does
resolve to 127.0.0.1.

"Protocol not supported" suggests to me that getaddrinfo is returning an
IPv6 address for localhost when your kernel only supports IPv4 (or
possibly vice versa, but that seems much less likely). You didn't give
enough detail to help in explaining why that might happen...

I do see a lot of failed connection attempts to port 53 from
postgres.

If you are intending to run without DNS, then you need to create or
adjust your /etc/resolv.conf file to say so.

regards, tom lane

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Tom Lane (#2)
Re: could not create socket for statistics collector: Protocol not supported

In a moment of brain fade I wrote:

If you are intending to run without DNS, then you need to create or
adjust your /etc/resolv.conf file to say so.

Er, make that "/etc/nsswitch.conf" ...

regards, tom lane