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.
