EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Posted: 2023-03-28 09:26 AM . Last Modified: 2023-05-02 11:45 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-03-28 09:26 AM . Last Modified: 2023-05-02 11:45 PM
Hello
After a server disconnection event in a SCADA system. When server 1 wanted to go from MAIN to STANDBY state, an error occurred and the image warning jumped.
Server 1 went to invalid database state. The scada 1 service was turned off and re-uploaded, server 1 went to standby status.
Server 1 can be turned on as main without problems, and goes to standby if Server 2 is as Main.
Please your help with the possible causes of this problem and how to mitigate it. The log is shared around the event. which occurred between 10:40 a.m. and 10:47 a.m., the time at which the service was lowered.
27-MAR-2023 15:44:42.696 080C [STBYMON] Main Link INTERSCX01 (Monitor Connect Timeout 60, Monitor Request Timeout 240, Compressed) GetRemoteServerState: State 21, Start 16-MAR-2023 21:35:44.425, StateChange 16-MAR-2023 21:44:28.817, WentMain 16-MAR-2023 21:44:28.817, Priority 1, Arbitrate = true)
27-MAR-2023 15:44:42.696 080C [STBYMON] Main Link INTERSCX01 (Monitor Connect Timeout 60, Monitor Request Timeout 240, Compressed) Get Remote Link Configuration
27-MAR-2023 15:44:42.712 08B0 [STBYLINK] A Old State 2 (Offline), New State 4 (Main)
27-MAR-2023 15:44:42.712 08B0 [STATE] State 21 (Main), Event 4 (A Main), Next State 21 (Main)
27-MAR-2023 15:44:42.712 08B0 [STATE] Action 12 (Arbitrate Main Main with A)
27-MAR-2023 15:44:42.712 08B0 [STATE] This node 'INTERSCX02', priority 0, StartTime 27-MAR-2023 15:03:07.395, TimeWentMain 27-MAR-2023 15:43:02.137
27-MAR-2023 15:44:42.712 08B0 [STATE] Partner A node 'INTERSCX01', priority 1, StartTime 16-MAR-2023 21:35:44.425, TimeWentMain 16-MAR-2023 21:44:28.817
27-MAR-2023 15:44:42.712 08B0 [STATE] Lost Arbitration (Main Isolated) With A (INTERSCX01)
27-MAR-2023 15:44:42.712 08B0 [STATE] Lost Arbitration With A (INTERSCX01)
27-MAR-2023 15:44:42.712 08B0 [STATE] State 21 (Main), Event 11 (Lose to A), Next State 36 (Losing to A)
27-MAR-2023 15:44:42.712 1E68 [STBYLINK] A Link 1 (Main) Heartbeat Connect To INTERSCX01(192.168.11.5), Heartbeat Connect Timeout 60, Heartbeat Request Timeout 5000, Heartbeat Interval 5000, Compressed
27-MAR-2023 15:44:42.712 08B0 [STATE] Action 2 (Now Standby)
27-MAR-2023 15:44:42.712 08B0 [STATE] Summary State 3 (Main), Event 2 (Standby), Next Summary State 4 (Synchronising Data)
27-MAR-2023 15:44:42.712 08B0 [SVRADVISE] A01#04 SendEvent: EVT_SCX_STATECHANGE (272 bytes) to ClientId 74 (1 events queued)
27-MAR-2023 15:44:42.712 08B0 [SVRADVISE] A02#00 SendEvent: EVT_SCX_STATECHANGE (272 bytes) to ClientId 873 (1 events queued)
27-MAR-2023 15:44:42.712 08B0 [SVRADVISE] A03#15 SendEvent: EVT_SCX_STATECHANGE (272 bytes) to ClientId 75 (1 events queued)
27-MAR-2023 15:44:42.712 1E68 [STBYLINK] A Link 1 (Main) Creating new child link for connection to 192.168.11.5:5481
Line #8749 to #8765
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-08-11 05:33 AM
I hope the SE support team were able to help you with your request.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.