Disconnecting Exinda Mobile Server Peers Seen in Logs.

Summary

In the Exinda Mobile Server log, it is possible to see when other server peers are disconnecting from it.

Overview

Exinda Mobile uses the concept of Mobile Servers and Mobile Managers in order to properly function. Mobile Servers, which typically stand in front of application servers - that are, applications to be accelerated such as a CIFS File Share, can also be peered together if they are managed by the same Exinda Mobile Manager. Peered in this context rmeans that one server is creating a link and another server is the recipient of that link. The links can have two directions - unidirectional or bidirectional. In the unilateral case, the link creator can see the applications attached to the other Mobile Server. In the bidirectional case, both can see applications from each other.

Occasionally these peers can disconnect from one another due to various reasons, whether it is because of the peer being turned off or having a bad connection, etc. The following is logged on the remaining peer:

2016-04-05 05:10:30.200 [info] <0.85.0> softwoc_stats_collector INFO: User ["GRJM2G8H9ST1fMiDRRLg_w=="] with username ["exinda-mobile-server\\\\PEER"] has disconnected.

The user is a unique GUID that the peers generate so that it can easily be distinguished from standard client traffic. The username is another identifier from the end users. In the case of peers, as seen above, it will reflect its peer status. If the above message occurs, the peer has disconnected itself from the one seeing the message. While the latter will have no more logs regarding this incident, they might be found on the disconnected peer, and as mentioned, they can be due to the peer rebooting, the peer losing connection over the WAN, or other numerous reasons.