pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgdg96 repo with centos 7.x - server starts only on loopback 3+ messages / 3 participants [nested] [flat]
* pgdg96 repo with centos 7.x - server starts only on loopback @ 2017-07-28 14:59 lejeczek <peljasz@yahoo.co.uk> 0 siblings, 1 reply; 3+ messages in thread From: lejeczek @ 2017-07-28 14:59 UTC (permalink / raw) To: pgsql-admin hi fellas 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 all I have to do is to: $ systemctl restart postgresql-9.6 to get expected results. Is this not bizarre? I peep into systemd's Unit and there: ... [Unit] Description=PostgreSQL 9.6 database server After=syslog.target After=network.target seems ok, right? What can be wrong? many thank L. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: pgdg96 repo with centos 7.x - server starts only on loopback @ 2017-07-28 21:55 Tom Lane <tgl@sss.pgh.pa.us> parent: lejeczek <peljasz@yahoo.co.uk> 0 siblings, 1 reply; 3+ messages in thread From: Tom Lane @ 2017-07-28 21:55 UTC (permalink / raw) To: lejeczek <peljasz@yahoo.co.uk>; +Cc: pgsql-admin 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 ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: pgdg96 repo with centos 7.x - server starts only on loopback @ 2017-07-28 22:19 Scott Whitney <scott@journyx.com> parent: Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 3+ messages in thread From: Scott Whitney @ 2017-07-28 22:19 UTC (permalink / raw) To: Tom Lane <tgl@sss.pgh.pa.us>; lejeczek <peljasz@yahoo.co.uk>; +Cc: pgsql-admin Is SELINUX on? ________________________________ From: pgsql-admin-owner@postgresql.org <pgsql-admin-owner@postgresql.org> on behalf of Tom Lane <tgl@sss.pgh.pa.us> Sent: Friday, July 28, 2017 4:55 PM To: lejeczek Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] pgdg96 repo with centos 7.x - server starts only on loopback 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 Journyx, Inc. 7600 Burnet Road #300 Austin, TX 78757 www.journyx.com p 512.834.8888 f 512-834-8858 Do you receive our promotional emails? Click here <http://journyx.com/communication-preferences; or visit http://journyx.com/communication-preferences to unsubscribe. ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2017-07-28 22:19 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2017-07-28 14:59 pgdg96 repo with centos 7.x - server starts only on loopback lejeczek <peljasz@yahoo.co.uk> 2017-07-28 21:55 ` Tom Lane <tgl@sss.pgh.pa.us> 2017-07-28 22:19 ` Scott Whitney <scott@journyx.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox