From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problem with pl/python procedure connecting to the internet |
Date: | 2015-08-23 18:13:43 |
Message-ID: | 55DA0D57.3050508@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/23/2015 10:49 AM, Tom Lane wrote:
> However, what this smells like to me is a permissions problem. I think
> you were way too quick to dismiss the idea that SELinux (or something
> just like it) is restricting outbound internet connections from Postgres.
> It's standard for SELinux to be configured so that network-accessible
> daemons like Postgres are locked down harder than the very same code
> would be treated when being invoked from the command line --- and network
> access would be one of the prime candidates to be disabled by default.
>
> Have you poked around under/var/log/ to see if the kernel logs anything
> when the connection attempt doesn't work? For that matter, have you
> checked the postmaster log to see what Postgres logs about it?
also, `getenforce` ... if it comes back enabled, as root, do...
setenforce permissive
and try your trigger again (don't reboot or restart anything, just do it)
--
john r pierce, recycling bits in santa cruz
From | Date | Subject | |
---|---|---|---|
Next Message | Pande, Nitin | 2015-08-23 18:16:34 | AIX 7.1 compile and initdb startup error TRAP: FailedAssertion |
Previous Message | Tom Lane | 2015-08-23 17:49:54 | Re: Problem with pl/python procedure connecting to the internet |