Description of problem: In case, during glusterd restart in case host resolution fails, it's difficult to identify for which brick and the volume the resolution has failed. Until and unless glusterd is run in debug mode the sufficient logs can't be captured. This bug is to track this missing information in the log. Version-Release number of selected component (if applicable): release-6
REVIEW: https://review.gluster.org/22181 (glusterd: improve logging) posted (#1) for review on release-6 by Atin Mukherjee
REVIEW: https://review.gluster.org/22181 (glusterd: improve logging) merged (#2) on release-6 by Shyamsundar Ranganathan
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 [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/