**** **** -- no connection **** Report from: stdb_pg, Status: STDB_ERR ****Postgres connect error **** **** -- no connection **** Report from: stdb_pg_conn, Status: STDB_ERR ****Couldn't connect with server **** **** -- no connection **** Report from: stdb_pg, Status: STDB_ERR ****Postgres connect error **** **** -- no connection **** Report from: stdb_pg_conn, Status: STDB_ERR ****Couldn't connect with server **** **** -- no connection **** Report from: stdb_pg, Status: STDB_ERR ****Postgres connect error **** **** -- no connection **** Report from: stdb_pg_conn, Status: STDB_ERR ****Couldn't connect with server **** **** -- no connection **** Report from: stdb_pg, Status: STDB_ERR ****Postgres connect error **** **** -- no connection **** Report from: stdb_pg_conn, Status: STDB_ERR ****Couldn't connect with server **** **** -- no connection **** Report from: stdb_conn_dbms, Status: STDB_ERR ****No server is available for connection **** **** -- no connection **** Report from: stdb_pg, Status: STDB_ERR ****Postgres connect error **** **** -- no connection **** Report from: stdb_pg_conn, Status: STDB_ERR ****Couldn't connect with serverIf you can't find a solution, report to CDS and insert into your message the following details:
.errorfile=/tmp/VR1546842.err (2025-07-11T22:06:27) -3 -source=J/MNRAS/504/2420/tablea2 -ref=VIZ68718ae3179a5a