org.postgresql.util.PSQLException

FATAL: no pg_hba.conf entry for host "127.0.0.1", user "dspace-cris", database "dspace-cris", SSL off

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web60

  • via Unknown by Yen-Tang Chen,
  • Stack trace

    • org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "127.0.0.1", user "dspace-cris", database "dspace-cris", SSL off at org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:2585) at org.dspace.app.cris.discovery.CrisSearchService.renewMetricsCache(CrisSearchService.java:1026) at org.dspace.app.cris.statistics.plugin.StatsPercentileIndicatorsPlugin.buildIndicator(StatsPercentileIndicatorsPlugin.java:95) at org.dspace.app.cris.batch.ScriptStatsMetrics.main(ScriptStatsMetrics.java:134) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78) Caused by: org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "127.0.0.1", user "dspace-cris", database "dspace-cris", SSL off at org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:552) at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210) at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206) at org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:91) at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:301) at org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:2580) ... 9 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    4 more bugmates