Regards, Adrian, Tom and all pgsql-general list.
Like Tom said, the problem was with SELinux and I found the policy which caused all problems:
grep denied audit.log | audit2allow
#============= postgresql_t ==============
#!!!! This avc can be allowed using the boolean 'nis_enabled'
allow postgresql_t ephemeral_port_t:tcp_socket name_connect;
#!!!! This avc can be allowed using the boolean 'nis_enabled'
allow postgresql_t unreserved_port_t:tcp_socket name_connect;
I checked that boolean with:
# getsebool -a | grep nis_enabled
nis_enabled --> off
Then, I changed it to on, and everything works well with SELinux enabled by default.
Thanks again for the time and patience.
On 24/05/15 19:43, Adrian Klaver wrote:
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>