[Bugs] [Bug 1283833] New: Warning messages seen in glusterd logs in executing gluster volume set help
bugzilla at redhat.com
bugzilla at redhat.com
Fri Nov 20 04:13:25 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1283833
Bug ID: 1283833
Summary: Warning messages seen in glusterd logs in executing
gluster volume set help
Product: GlusterFS
Version: 3.7.6
Component: core
Keywords: Triaged
Severity: medium
Assignee: bugs at gluster.org
Reporter: amukherj at redhat.com
CC: amukherj at redhat.com, bugs at gluster.org,
gluster-bugs at redhat.com, nlevinki at redhat.com,
olim at redhat.com, rhs-bugs at redhat.com,
sasundar at redhat.com, vbellur at redhat.com
Depends On: 1283485
Blocks: 1243351
+++ This bug was initially created as a clone of Bug #1283485 +++
+++ This bug was initially created as a clone of Bug #1243351 +++
Description of problem:
-----------------------
gluster volume set help fails to find certain shared object (so) files and log
a warning message
However there is no functional impact
Version-Release number of selected component (if applicable):
-------------------------------------------------------------
Mainline
How reproducible:
-----------------
Always
Steps to Reproduce:
-------------------
Execute gluster volume set help
Actual results:
---------------
Warning messages are seen in glusterd logs (
/var/log/glusterfs/etc-glusterfs-glusterd.vol.log as below :
<snip>
[2015-07-15 11:48:38.130329] W [MSGID: 101095]
[xlator.c:143:xlator_volopt_dynload] 0-xlator:
/usr/lib64/glusterfs/3.7.1/xlator/rpc-transport/socket.so: cannot open shared
object file: No such file or directory
[2015-07-15 11:48:38.223781] W [MSGID: 101095]
[xlator.c:143:xlator_volopt_dynload] 0-xlator:
/usr/lib64/glusterfs/3.7.1/xlator/configuration.so: cannot open shared object
file: No such file or directory
[2015-07-15 11:48:42.822541] I [MSGID: 106487]
[glusterd-handler.c:1402:__glusterd_handle_cli_list_friends] 0-glusterd:
Received cli list req
[2015-07-15 11:48:38.130383] W [MSGID: 101095]
[xlator.c:143:xlator_volopt_dynload] 0-xlator:
/usr/lib64/glusterfs/3.7.1/xlator/rpc-transport/socket.so: cannot open shared
object file: No such file or directory
[2015-07-15 11:48:38.223849] W [MSGID: 101095]
[xlator.c:143:xlator_volopt_dynload] 0-xlator:
/usr/lib64/glusterfs/3.7.1/xlator/configuration.so: cannot open shared object
file: No such file or directory
</snip>
--- Additional comment from Vijay Bellur on 2015-11-19 01:37:57 EST ---
REVIEW: http://review.gluster.org/12656 (core : Use correct path in dlopen for
socket.so) posted (#1) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Niels de Vos on 2015-11-19 04:02:37 EST ---
Please provide a public description of the issue, including error messages and
the like. This makes it possible for other users to find this bug.
--- Additional comment from Vijay Bellur on 2015-11-19 10:18:34 EST ---
COMMIT: http://review.gluster.org/12656 committed in master by Jeff Darcy
(jdarcy at redhat.com)
------
commit 5dd1ecae7519f9d3910962d310356e07902a8fd0
Author: Atin Mukherjee <amukherj at redhat.com>
Date: Thu Nov 19 12:00:23 2015 +0530
core : Use correct path in dlopen for socket.so
This patch fixes the path for socket.so file while loading the so
dynamically.
Also for config.memory-accounting & config.transport voltype is changed to
glusterd to fix the warning message coming from xlator_volopt_dynload
Change-Id: I0f7964814586f2018d4922b23c683f4e1eb3098e
BUG: 1283485
Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-on: http://review.gluster.org/12656
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Niels de Vos <ndevos at redhat.com>
Reviewed-by: Jeff Darcy <jdarcy at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1243351
[Bug 1243351] Warning messages seen in glusterd logs when installed from
RHGS 3.1 ISO based on RHEL 7.1
https://bugzilla.redhat.com/show_bug.cgi?id=1283485
[Bug 1283485] Warning messages seen in glusterd logs in executing gluster
volume set help
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list