From: Tom Lane <tgl@sss.pgh.pa.us>
To: lejeczek <peljasz@yahoo.co.uk>
cc: pgsql-admin@postgresql.org
Subject: Re: pgdg96 repo with centos 7.x - server starts only on loopback
In-reply-to: <14ccdc33-9442-5955-ebdd-4a68a43f5102@yahoo.co.uk>
References: <14ccdc33-9442-5955-ebdd-4a68a43f5102@yahoo.co.uk>
Comments: In-reply-to lejeczek <peljasz@yahoo.co.uk>
	message dated "Fri, 28 Jul 2017 15:59:52 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <19998.1501278926.1@sss.pgh.pa.us>
Date: Fri, 28 Jul 2017 17:55:26 -0400
Message-ID: <19999.1501278926@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

lejeczek <peljasz@yahoo.co.uk> writes:
> I'm using PostgreSQL 9.6 7 - x86_64 repo with centos 7.3.
> Configuration pretty standard, including this among the lines:
> ...
> listen_addresses = 'localhost, 192.168.2.200, 10.5.6.100'
> ...
> and yet, after system reboot I get process listening only on:

> tcp        0      0 127.0.0.1:15432         0.0.0.0:* 
> LISTEN      5373/postmaster
> tcp6       0      0 ::1:15432               :::* LISTEN      
> 5373/postmaster

> What can be wrong?

Looking into the postmaster's log would be informative, but I suspect
what is happening is that systemd is allowing the postmaster to start
before those non-default interfaces are up.  This is one of the ways
systemd sucks :-( ... it's actually quite hard to prevent that.
"After=network.target" does *not* do it, at least not without munging
the definition of that target.

I don't offhand recall the solution for this, but it's a systemd
question not a Postgres question.  Googling on that basis might help.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin