Re: Unable to start postgresql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Iliffe <john(dot)iliffe(at)iliffe(dot)ca>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unable to start postgresql
Date: 2017-03-09 05:28:16
Message-ID: 30955.1489037296@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

John Iliffe <john(dot)iliffe(at)iliffe(dot)ca> writes:
> On Wednesday 08 March 2017 23:35:10 Tom Lane wrote:
>> That isn't proving a lot: as I showed in my example lsof output,
>> Fedora's lsof will map "5432" to "postgres" in the context of an IP
>> port number. (I'm sure there's a way to turn that off, but -n ain't
>> it.)

> Yes, but your lsof output also showed a line for postmaster and mine
> doesn't.

That's because I started mine by saying "postmaster" not "postgres".
It's not real relevant, just ancient habit of mine.

> In your case postmaster has an IPv6 TCP socket (but no IPv4 I
> notice)

Uh, what? I showed an IPv6, an IPv4, and a Unix socket.

> The following is from ss, the new version of netstat:
> ------------------------------------
> tcp LISTEN 0 128 127.0.0.1:postgres *:*
> tcp LISTEN 0 128 ::1:postgres :::*
> ------------------------------------

Well, that's pretty interesting, because it proves that *something* has
got IPv4 port 5432 open. If not your manually-started postmaster, then
what? You need to inquire into that a bit harder. Running lsof as root
and examining all processes might help.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message vinny 2017-03-09 10:15:23 Re: count case when - PG 9.2
Previous Message hariprasath nallasamy 2017-03-09 05:25:36 Re: too may LWLocks