Search Engine: Elastic

Article ID: 132499, created on Apr 11, 2018, last review on Apr 11, 2018

  • Applies to:
  • Operations Automation

Symptoms

An Order on the Billing side fails:

SQLGrammarException: could not extract ResultSet

core.log reveals the following exception reason:

Caused by: org.postgresql.util.PSQLException: ERROR: relation "addresses_address_id_seq" does not exist
  Position: 16
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288)

console.log since the last pau service restart:

Caused by: org.postgresql.util.PSQLException: Connection to 192.168.0.1:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
...
Caused by: java.net.ConnectException: Connection refused (Connection refused)

Cause

Postgresql service(postmaster) was not started or did not start correctly since pau service latest restart.

Resolution

Make sure Postgresql service is up and running and restart OA services using instructions from How to restart OA system services: UI, Management Node, Agents

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF