+++ 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) --- 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) ------ commit 5dd1ecae7519f9d3910962d310356e07902a8fd0 Author: Atin Mukherjee <amukherj> 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> Reviewed-on: http://review.gluster.org/12656 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Jeff Darcy <jdarcy>
REVIEW: http://review.gluster.org/12671 (core : Use correct path in dlopen for socket.so) posted (#1) for review on release-3.6 by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/12671 committed in release-3.6 by Raghavendra Bhat (raghavendra) ------ commit b19a1d0798aef65c07171492f7e3faaf3af6fed3 Author: Atin Mukherjee <amukherj> Date: Thu Nov 19 12:00:23 2015 +0530 core : Use correct path in dlopen for socket.so Backport of http://review.gluster.org/12656 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: 1283834 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/12656 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Jeff Darcy <jdarcy> Reviewed-on: http://review.gluster.org/12671 Reviewed-by: Raghavendra Bhat <raghavendra>
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-v3.6.8, please open a new bug report. glusterfs-v3.6.8 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://www.gluster.org/pipermail/gluster-users/2016-January/025161.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user