Actions
Incident #12696
closed
geonetwork-spatialdata.d4science.org denied access to database
Status:
Closed
Priority:
Urgent
Assignee:
_InfraScience Systems Engineer
Category:
Application
Target version:
Start date:
Oct 15, 2018
Due date:
% Done:
100%
Estimated time:
Infrastructure:
Production
Description
Node configuration seems faulty. From logs I can see the following error (seemingly the cause of other following ones) :
Cannot create PoolableConnectionFactory (FATAL: no pg_hba.conf entry for host "146.48.123.40", user "geonetwork-spatialdata-lab", database "geonetwork-spatialdata-lab", SSL off)
Updated by Andrea Dell'Amico over 6 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 100
I just reloaded the postgresql service to be on the safe side, but in the logs I saw:'
2018-10-15 16:59:43.413 CEST [19806] geonetwork-spatialdata-lab@geonetwork-spatialdata-lab LOG: connection authorized: user=geonetwork-spatialdata-lab database=geonetwork-spatialdata-lab 2018-10-15 16:59:43.413 CEST [19803] geonetwork-spatialdata-lab@geonetwork-spatialdata-lab LOG: connection authorized: user=geonetwork-spatialdata-lab database=geonetwork-spatialdata-lab 2018-10-15 16:59:44.852 CEST [19808] [unknown]@[unknown] LOG: connection received: host=geonetwork-spatialdata.d4science.org port=60133 2018-10-15 16:59:44.854 CEST [19808] geonetwork-spatialdata-lab@geonetwork-spatialdata-lab LOG: connection authorized: user=geonetwork-spatialdata-lab database=geonetwork-spatialdata-lab
I reloaded the service after that time.
Updated by Fabio Sinibaldi over 6 years ago
- Status changed from In Progress to Closed
GeoNetwork is now connected and the error is no more stated in the webapp logs.
Actions
