• Replies 7 replies
  • Subscribers 582 subscribers
  • Views 497 views
  • Users 0 members are here
Options
Related

Running multiple clusters on a single server pairs on CitectSCADA 2018 R2

Chris

I had 3 clusters setup running fine in a test environment on V8.1 on the latest update. Today, I upgraded to v8.2, ever since, the alarms don't work, be the Example_SA project alarms work fine. I looked in the trace logs for the alarm server, there are countless errors with refused connections, the firewall is disabled on my machine too. It's not a privilege issue either.

2019-09-11 13:44:22.941 -07:00 21256 0 Error Transport TcpipTransport::EndConnect() [CLIENT 0.0.0.0:57459 --> 127.0.0.1:2082 #1] SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:2082
2019-09-11 13:44:25.168 -07:00 27936 0 Error Transport TcpipTransport::EndConnect() [CLIENT 0.0.0.0:57472 --> 127.0.0.1:12082 #2] SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:12082
2019-09-11 13:44:27.424 -07:00 15584 0 Error Transport TcpipTransport::EndConnect() [CLIENT 0.0.0.0:57492 --> 127.0.0.1:22082 #3] SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:22082

I had to manually define the port numbers 12080 and 22082 for cluster 2 and 3 respectfully. Again, this work perfectly in v8.1.

I also get a hardware alarm from each of the running Alarm servers - Data Not Ready.

Parents
  • Hi Chris,
    I'm still a little confused how you could have compiled your project in Citect SCADA 2018 (8.10) without defining the Port, Legacy Port and Database Port for the additional Clusters. If you leave them blank, they assume the default value of 2080, 2076 and 5482 respectively. But in your configuration, you have 3 clusters all on the same machine, which if left blank, would all assume the same value and have a conflict. You would not be able to compile this project without receiving the error: "E2092 - A server with this network address and port already exists". So when running more than one cluster on the same machine, you must define unique ports. Have you modified the topology during the upgrade? As Bradley asked previously, it would also be good to know how many network cards you have and the number of machines in the system.
    It is very interesting that there is a different between running stand-alone ([LAN]TCPIP=0) and networked mode ([LAN]TCPIP=1). It is worth checking the DNS name field is set correctly.
Reply
  • Hi Chris,
    I'm still a little confused how you could have compiled your project in Citect SCADA 2018 (8.10) without defining the Port, Legacy Port and Database Port for the additional Clusters. If you leave them blank, they assume the default value of 2080, 2076 and 5482 respectively. But in your configuration, you have 3 clusters all on the same machine, which if left blank, would all assume the same value and have a conflict. You would not be able to compile this project without receiving the error: "E2092 - A server with this network address and port already exists". So when running more than one cluster on the same machine, you must define unique ports. Have you modified the topology during the upgrade? As Bradley asked previously, it would also be good to know how many network cards you have and the number of machines in the system.
    It is very interesting that there is a different between running stand-alone ([LAN]TCPIP=0) and networked mode ([LAN]TCPIP=1). It is worth checking the DNS name field is set correctly.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.