PVSS00event - REDU/SEVERE - EventManager, redPeerGot, We got connection to redundant peer, but we are not buffering msgs

Enclosed you'll find the explanation for a log-message which occurs when the connection between two redundant servers is reestablished.
The messages are written to the PVSS_II.log-file.

PVSS00event (0), 2011.06.27 17:52:25.644, REDU, SEVERE, 54, Unexpected state, EventManager, redPeerGot, We got connection to redundant peer, but we are not buffering msgs - committing suicide

PVSS00event (0), 2011.07.22 14:21:12.388, REDU, SEVERE, 54, Unexpected state, EventManager, redPeerGot, We got connection to redundant peer, but we are not buffering msgs - shutting the peer down

Log-message with symbolic names:

PVSS00event (0), <TIMESTAMP>, REDU, SEVERE, 54, Unexpected state, EventManager, redPeerGot, We got connection to redundant peer, but we are not buffering msgs - committing suicide

This log-message describes that the connection was reestablished and the own server is restarted.

PVSS00event (0), <TIMESTAMP>, REDU, SEVERE, 54, Unexpected state, EventManager, redPeerGot, We got connection to redundant peer, but we are not buffering msgs - shutting the peer down

This log-message describes that the connection was reestablished and the other server is restarted. On the other server you should see a log-message that the signal 15 was received and the event-manager is exiting afterwards.

Network problems could be a cause that the connection was lost. Please check the network to ensure that the network connections are stable.