From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | lejeczek <peljasz(at)yahoo(dot)co(dot)uk> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pgdg96 repo with centos 7.x - server starts only on loopback |
Date: | 2017-07-28 21:55:26 |
Message-ID: | 19999.1501278926@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
lejeczek <peljasz(at)yahoo(dot)co(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Whitney | 2017-07-28 22:19:40 | Re: pgdg96 repo with centos 7.x - server starts only on loopback |
Previous Message | Riceal McDermott | 2017-07-28 15:28:25 | Postgres SQL - Certification query |