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:
Patches in master http://review.gluster.org/10042 http://review.gluster.org/11280
Patch that fixes in downstream: https://code.engineering.redhat.com/gerrit/#/c/50886/ (Merged) https://code.engineering.redhat.com/gerrit/#/c/51100/ (Merged)
Please provide information such as what needs to verified. there is no problem description available/steps..
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 client log messaging: the messages id was verified with the corresponding label.. 2015-07-06 03:33:11.259462] I [MSGID: 101190] [event-epoll.c:632:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2015-07-06 03:33:11.270045] I [MSGID: 101190] [event-epoll.c:632:event_dispatch_epoll_worker] 0-epoll: Started thread with index 2 [2015-07-06 03:33:11.270614] I [MSGID: 114020] [client.c:2118:notify] 0-lot-client-0: parent translators are ready, attempting connect on transport [2015-07-06 03:33:11.273115] I [MSGID: 114020] [client.c:2118:notify] 0-lot-client-1: parent translators are ready, attempting connect on transport [root@casino-vm2 glusterfs]# 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 glusterfs]#
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