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

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
  • It looks like the Alarm Server can't connect to the IO Servers. Can you confirm you have rebooted the machine after installing Citect SCADA 2018 R2? Yes

    You also need to ensure that the Windows User accounts are added to the appropriate Citect User Groups depending on the role they play. See "Post Installation Configuration" in the help for information on configuring this. Done

    Did you run Configurator and setup security? Yes If you want to disable security, you still need to set System Management Server to "Not Configured" and then untick encryption in the Encryption section.

    Finally, run the computer setup wizard and run again. Done that.

    What did you mean by manually define port numbers? In the project configuration? For each Alarm Server? Which column / field? Topology>Edit>Alarm Servers>[Port,Legacy Port, Database Port].

    Oh, and I found that this is only an issue running as a Stand-Alone system, the issue goes away once I configure it to be networked, never had that issue on past versions.

Reply
  • It looks like the Alarm Server can't connect to the IO Servers. Can you confirm you have rebooted the machine after installing Citect SCADA 2018 R2? Yes

    You also need to ensure that the Windows User accounts are added to the appropriate Citect User Groups depending on the role they play. See "Post Installation Configuration" in the help for information on configuring this. Done

    Did you run Configurator and setup security? Yes If you want to disable security, you still need to set System Management Server to "Not Configured" and then untick encryption in the Encryption section.

    Finally, run the computer setup wizard and run again. Done that.

    What did you mean by manually define port numbers? In the project configuration? For each Alarm Server? Which column / field? Topology>Edit>Alarm Servers>[Port,Legacy Port, Database Port].

    Oh, and I found that this is only an issue running as a Stand-Alone system, the issue goes away once I configure it to be networked, never had that issue on past versions.

Children
No Data