Red Hat Bugzilla – Bug 1246946
critical message seen in glusterd log file, when detaching a peer, but no functional loss
Last modified: 2015-10-05 03:21:15 EDT
Description of problem: ------------------------ While detaching a peer from host1, critical error message is seen in glusterd logs in same host. Functionally wasn't affected but these critical error messages should not be seen in glusterd logs Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHGS 3.1 How reproducible: ------------------ Always Steps to Reproduce: ------------------- 1. Detach a peer from the cluster 2. Observe glusterd logs Actual results: --------------- Critical message was seen in glusterd logs as follows : "[2015-07-26 09:10:29.584438] C [MSGID: 106129] [glusterd-handler.c:5019:__glusterd_peer_rpc_notify] 0-management: Could not find peer dhcp37-58.lab.eng.blr.redhat.com(00000000-0000-0000-0000-000000000000) [No such file or directory]" Expected results: ------------------ There shouldn't be any critical messages
An upstream patch http://review.gluster.org/#/c/10272/ is been already posted for this.
Downstream patch : https://code.engineering.redhat.com/gerrit/55047
Version used to Verify this bug is glusterfs-3.7.1-12. No more we are seeing this issue, Moving this bug to Verified state.
Atin, I see the doc_text is explaining lots of technical information. It could be concise explaining the actual problem
(In reply to SATHEESARAN from comment #6) > Atin, > > I see the doc_text is explaining lots of technical information. > It could be concise explaining the actual problem Its just that we should remove the log instance here, apart from that I don't think other stuffs are technical. Divya, Could you reword the doc text as : "Previously, while detaching a peer from a node, glusterd service was logging a critical message saying could not find the peer. With this fix, glusterd service doesn't log this error."
(In reply to Atin Mukherjee from comment #7) > (In reply to SATHEESARAN from comment #6) > > Atin, > > > > I see the doc_text is explaining lots of technical information. > > It could be concise explaining the actual problem > > Its just that we should remove the log instance here, apart from that I > don't think other stuffs are technical. > > Divya, > > Could you reword the doc text as : > "Previously, while detaching a peer from a node, glusterd service was > logging a critical message saying could not find the peer. With this fix, > glusterd service doesn't log this error." Thanks Atin and that looks simple and understandable for admin/user
Updated the doc text based on Comment 7.
Doc text signed off
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1845.html