Description of problem:
there's no way to identify between intentional and unintentional socket closure
logs at INFO log level helps identify voluntary socket closure
COMMIT: https://review.gluster.org/21481 committed in master by "Amar Tumballi" <email@example.com> with a commit message- transport: log socket closures more verbose
Intentional and unintentional socket closures cannot be identified
Log intentional socket closures with at least INFO log level
Signed-off-by: Milind Changire <firstname.lastname@example.org>
REVIEW: https://review.gluster.org/21665 (Revert \"transport: log socket closures more verbose\") posted (#1) for review on master by Milind Changire
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report.
glusterfs-6.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.