ModArcPostgreSql always connects to port 5432 instead of configured PostgreSQL p

[Andi]

Hello,

I am trying to use Rapid SCADA 6.2.2.1 on Ubuntu Server with a PostgreSQL database running in a Docker container on a Synology NAS.

Environment:
– Rapid SCADA Server 6.2.2.1
– Ubuntu Server 24.04
– PostgreSQL 18.4 in Docker on Synology DSM
– Database host: 192.168.1.4
– Database port: 15432
– Database: rapidscada
– User: scada

The PostgreSQL server is working correctly.

The following tests are successful:

– psql can connect successfully using host 192.168.1.4 and port 15432.
– The Deployment Profile database connection test succeeds when using a complete connection string:
Server=192.168.1.4;Port=15432;Database=rapidscada;User Id=scada;Password=…

ScadaInstanceConfig.xml contains:

<Connection>
<Name>MainConnection</Name>
<DBMS>PostgreSQL</DBMS>
<Server>192.168.1.4</Server>
<Database>rapidscada</Database>
<Username>scada</Username>
<ConnectionString />
</Connection>

The PostgreSQL connection itself works correctly.

However, after restarting ScadaServer, the archive modules always try to connect to:

192.168.1.4:5432

The log contains messages like:

Error calling the MakeReady method of the CurCopy archive:
Failed to connect to 192.168.1.4:5432
Connection refused

The same happens for:

– CurCopy
– MinCopy
– HourCopy
– DayCopy
– EventsCopy

The important point is that the configured PostgreSQL server listens on port 15432, not on 5432.

Question:

Does ModArcPostgreSql in version 6.2.2.1 always use the default PostgreSQL port (5432)?

Is there another configuration location for the archive modules where the PostgreSQL port must be configured?

Or is this a known issue fixed in newer versions?

Thank you very much.

[Author]

Posts