From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Marcos Ortiz <mlortiz(at)uci(dot)cu>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Trying to solve a SocketError [Errno 13] Permission with PL/Python in PostgreSQL 9.3 |
Date: | 2015-05-24 23:43:37 |
Message-ID: | 55626229.4000803@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/24/2015 04:15 PM, Marcos Ortiz wrote:
> Sorry for the late response.
>
>>
>> Not sure if it applies but see here:
>>
>> http://neo4j.com/docs/stable/rest-api-security.html
>> "When Neo4j is first installed you can authenticate with the default
>> user neo4j and the default password neo4j. However, the default
>> password must be changed (see the section called “User status and
>> password changing”) before access to resources will be permitted. ..."
> Yes, I changed the password.
> It seems that the problem was with SELinux.
> I disabled it for a moment to make a simple test y everything worked.
> But, like Tom said, I don´t want SELinux disabled in my systems, so I
> will find out the
> security label who is blocking this in CentOS, and enable it again.
> When I find it, I will send the solution to the list.
Glad you found the cause and thanks for following up. Nice to be able to
close the loop on a problem.
> Best wishes and thanks again for your time.
>>
>>
>
> --
> Marcos Ortiz <http://about.me/marcosortiz>, Sr. Product Manager (Data
> Infrastructure) at UCI
> @marcosluis2186 <http://twitter.com/marcosluis2186>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Marcos Ortiz | 2015-05-25 05:22:20 | SOLVED: Trying to solve a SocketError [Errno 13] Permission with PL/Python in PostgreSQL 9.3 |
Previous Message | Marcos Ortiz | 2015-05-24 23:15:07 | Re: Trying to solve a SocketError [Errno 13] Permission with PL/Python in PostgreSQL 9.3 |