Redundant Server restarted by automatically

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
Search

Post Reply
2 posts • Page 1 of 1
paramesh1985
Posts: 67
Joined: Thu Sep 25, 2014 4:03 am

Redundant Server restarted by automatically

Post by paramesh1985 » Thu Jan 16, 2020 11:19 am

Hi

Could you please tell me the cause for the below error; due to this error redundant server got restarted by automatically

WCCILdata (0), 2020.01.15 21:24:38.607, SYS, SEVERE, 39, Connection lost, Alive timeout expired, closing connection to (SYS: 0 Data -num 0 CONN: 2) (P) @ X862KS0502 (::ffff:10.5.110.2). Last message expected at 2020.01.15 21:24:38.407.
WCCILredu (1), 2020.01.15 21:24:38.650, SYS, SEVERE, 39, Connection lost, Alive timeout expired, closing connection to (SYS: 20 Redu -num 1 CONN: 2) (P) @ X862KS0502 (10.5.110.2). Last message expected at 2020.01.15 21:24:38.648.
WCCILredu (1), 2020.01.15 21:24:38.650, SYS, SEVERE, 39, Connection lost, Alive timeout expired, closing connection to (SYS: 20 Redu -num 1 CONN: 2) (S) @ X862KS0502-2 (10.5.210.2). Last message expected at 2020.01.15 21:24:38.648.
WCCILredu (1), 2020.01.15 21:24:38.650, SYS, INFO, 63, Connection error, Closing connection to redundancy partner
WCCILevent (0), 2020.01.15 21:24:39.452, SYS, SEVERE, 39, Connection lost, Alive timeout expired, closing connection to (SYS: 20 Event -num 0 CONN: 2) (P) @ X862KS0502 (10.5.110.2). Last message expected at 2020.01.15 21:24:38.518.
WCCILevent (0), 2020.01.15 21:24:39.453, SYS, SEVERE, 39, Connection lost, Alive timeout expired, closing connection to (SYS: 20 Event -num 0 CONN: 2) (S) @ X862KS0502-2 (10.5.210.2). Last message expected at 2020.01.15 21:24:38.518.
WCCILevent (0), 2020.01.15 21:24:39.558, REDU, WARNING, 0, , Status change to active requested, no negotiation with redundant peer possible
WCCILevent (0), 2020.01.15 21:24:39.558, REDU, INFO, 0, , Status changed to ACTIVE
WCCOAsnmp (3), 2020.01.15 21:24:39.568, SYS, INFO, 0, , AgentList, goActive, Becoming active
WCCOAsnmp (3), 2020.01.15 21:24:39.568, SYS, INFO, 0, , V3AgentList, goActive, Becoming active
WCCOAiec (1), 2020.01.15 21:24:39.569, PARAM,INFO, 54, Unexpected state, IecHWService, notifyDisableCommands, Getting active. Waiting 2 seconds before starting connections.
WCCILsplit (2), 2020.01.15 21:24:47.774, SYS, SEVERE, 63, Connection error, Connection reset by peer (10054)
WCCILsplit (2), 2020.01.15 21:24:47.774, SYS, SEVERE, 63, Connection error, Connection reset by peer (10054)
WCCILsplit (2), 2020.01.15 21:24:47.774, SYS, SEVERE, 63, Connection error, Connection reset by peer (10054)
WCCILsplit (2), 2020.01.15 21:24:47.774, SYS, SEVERE, 63, Connection error, Connection reset by peer (10054)
WCCILsplit (2), 2020.01.15 21:24:47.774, SYS, SEVERE, 63, Connection error, Connection reset by peer (10054)
WCCILsplit (2), 2020.01.15 21:24:47.775, SYS, SEVERE, 63, Connection error, Connection reset by peer (10054)
WCCILsplit (2), 2020.01.15 21:24:47.775, SYS, SEVERE, 63, Connection error, Connection reset by peer (10054)
WCCILsplit (2), 2020.01.15 21:24:47.775, SYS, SEVERE, 63, Connection error, Connection reset by peer (10054)

User avatar
leoknipp
Posts: 2245
Joined: Tue Aug 24, 2010 5:28 pm

Re: Redundant Server restarted by automatically

Post by leoknipp » Thu Jan 16, 2020 2:13 pm

The error you see in the first log messages that the alive timeout has expired.
In a redundant system you need to check also the logs for the other server to see the cause.

If the problem occurs several times there is maybe a problem with the time synchronization in your system.

Best Regards
Leopold Knipp
Senior Support Specialist

Post Reply
2 posts • Page 1 of 1