Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The patch that fixes this can be found in: Master: http://review.gluster.org/#/c/9874/ Release-3.7: http://review.gluster.org/#/c/10552/
Patch that fixes in downstream: https://code.engineering.redhat.com/gerrit/#/c/50889/ (merged)
Please provide specific problem description/steps as to what needs to be verified.
Log directory of glusterfs is located in /var/log/glusterfs. With this patch, the log messages are enhanced with a unique message id(helps in easier diagnosis) which was not present in the previous logs. With the patch, the logging messages are ported to a new framework.
this is related to protocol server messaging: the log contains message id which is verified with the label.: [2015-07-06 03:19:35.113278] I [MSGID: 115034] [server.c:397:_check_for_auth_option] 0-/rhs/brick1/l0: skip format check for non-addr auth option auth.login./rhs/brick1/l0.allow [2015-07-06 03:19:35.113370] I [MSGID: 115034] [server.c:397:_check_for_auth_option] 0-/rhs/brick1/l0: skip format check for non-addr auth option auth.login.bee3bffe-c2bf-4098-b5bd-6db9c29710cd.password [2015-07-06 03:19:35.113374] I [MSGID: 101190] [event-epoll.c:632:event_dispatch_epoll_worker] 0-epoll: Started thread with index 2 [2015-07-06 03:19:35.130571] I [rpcsvc.c:2213:rpcsvc_set_outstanding_rpc_limit] 0-rpc-service: Configured rpc.outstanding-rpc-limit with value 64 [root@casino-vm2 bricks]# rpm -qa | grep gluster gluster-nagios-addons-0.2.3-1.el6rhs.x86_64 glusterfs-client-xlators-3.7.1-6.el6rhs.x86_64 glusterfs-server-3.7.1-6.el6rhs.x86_64 gluster-nagios-common-0.2.0-1.el6rhs.noarch glusterfs-3.7.1-6.el6rhs.x86_64 glusterfs-api-3.7.1-6.el6rhs.x86_64 glusterfs-cli-3.7.1-6.el6rhs.x86_64 glusterfs-geo-replication-3.7.1-6.el6rhs.x86_64 vdsm-gluster-4.16.20-1.1.el6rhs.noarch glusterfs-libs-3.7.1-6.el6rhs.x86_64 glusterfs-fuse-3.7.1-6.el6rhs.x86_64 glusterfs-rdma-3.7.1-6.el6rhs.x86_64 [root@casino-vm2 bricks]#
Not all instances of gf_log and gf_log_callingfn are ported to new logging framework. Raised the bug - https://bugzilla.redhat.com/show_bug.cgi?id=1242269 - to fix this issue
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-1495.html