Search Postgresql Archives

Re: could not bind IPv6 socket

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



hisatomo@xxxxxxxxxxx writes:
> Hi, Does anyone have any experience to see the messaege below?
> %pg_ctl start
> postmaster starting
> LOG:  could not bind IPv6 socket:
> HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.

Hmm, it's pretty odd that there's not any kernel errno message after
the "socket: ", but otherwise this is not very surprising.  There
are a lot of platforms where libc thinks that IPv6 sockets exist but
the kernel doesn't agree, and the above is the expected result in
such cases.  The postmaster will try to bind to the IPv6 address that
getaddrinfo() told it to try to bind to, fail, and emit a bleat like the
above.  As long as there is an IPv4 address we can successfully bind to,
no harm done.

> Does anyone know the way to make the log not appear?

Get your kernel and libc to agree about whether IPv6 is enabled.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux