Re: Trying to solve a SocketError [Errno 13] Permission with PL/Python in PostgreSQL 9.3
| От | Tom Lane |
|---|---|
| Тема | Re: Trying to solve a SocketError [Errno 13] Permission with PL/Python in PostgreSQL 9.3 |
| Дата | |
| Msg-id | 5001.1432420737@sss.pgh.pa.us обсуждение |
| Ответ на | Trying to solve a SocketError [Errno 13] Permission with PL/Python in PostgreSQL 9.3 (Marcos Ortiz <mlortiz@uci.cu>) |
| Ответы |
Re: Trying to solve a SocketError [Errno 13] Permission
with PL/Python in PostgreSQL 9.3
|
| Список | pgsql-general |
Marcos Ortiz <mlortiz@uci.cu> writes:
> O.S: CentOS 7 64 bits
> We are working here to integrate PostgreSQL with Neo4j through PL/Python
> using the py2neo module for it, and when we want to send sentences to
> Neo4j using port 7474, the executed code raises a SocketError [Errno 13]
> Permission denied.
> I tested the same code in a normal python script outside of PostgreSQL,
> and it works well, but the problem is when I use the code inside
> PostgreSQL with PL/Python.
Probably SELinux is set up to deny random connections originating from the
postgresql daemon. If disabling SELinux makes the problem go away then
that's it. (I do *not* recommend that as a permanent solution, of course.
You'll want to find some finer-grained change to the security policy.
Don't remember enough about SELinux to know what the most likely bet is.)
regards, tom lane
В списке pgsql-general по дате отправления: