| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | mattwelchwork(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16955: Replication port problems |
| Date: | 2021-04-08 15:15:34 |
| Message-ID: | 1847748.1617894934@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> Given that port 5123 is operative on the primary rather than the secondary,
> why should SELinux on the secondary be recording issues for port 5123 ?
This hardly seems like a bug. The entire *point* of SELinux is to prevent
daemon processes from doing unexpected things like connecting to ports
that they shouldn't.
> Issue is resolved by running "semanage port -a -t postgresql_port_t -p tcp
> 5123" on the secondary
And that's where you told SELinux it was okay. But I would not expect
the out-of-the-box configuration to allow this, and it didn't.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-04-08 16:04:35 | Re: BUG #16956: psql won't load command history |
| Previous Message | PG Bug reporting form | 2021-04-08 15:00:22 | BUG #16956: psql won't load command history |