Bug 1096026 - geo-rep: glusterd fails to start in source install.
Summary: geo-rep: glusterd fails to start in source install.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-09 06:49 UTC by Kotresh HR
Modified: 2014-11-11 08:32 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-11 08:32:12 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Kotresh HR 2014-05-09 06:49:20 UTC
Description of problem:
In source install, glusterd fails to start with followin error if libgfchangelog is not loaded in ldconfig.

[2014-05-09 05:41:38.442778] E [glusterd.c:397:glusterd_check_gsync_present] 0-glusterd: geo-replication module not working as desired
[2014-05-09 05:41:38.443082] D [glusterd.c:407:glusterd_check_gsync_present] 0-glusterd: Returning -1
[2014-05-09 05:41:38.443097] E [xlator.c:406:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again
[2014-05-09 05:41:38.443104] E [graph.c:322:glusterfs_graph_init] 0-management: initializing translator failed
[2014-05-09 05:41:38.443111] E [graph.c:525:glusterfs_graph_activate] 0-graph: init failed

gluster vol info (without staring glusterd) produces following trace.

[root@rhs1 glusterfs]# gluster vol info
Traceback (most recent call last):
  File "/usr/local/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 33, in <module>
    import resource
  File "/usr/local/libexec/glusterfs/python/syncdaemon/resource.py", line 37, in <module>
    from libgfchangelog import ChangelogException
  File "/usr/local/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 20, in <module>
    class Changes(object):
  File "/usr/local/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 21, in Changes
    libgfc = CDLL(find_library("gfchangelog"), use_errno=True)
  File "/usr/lib64/python2.6/ctypes/__init__.py", line 353, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: libgfchangelog.so.0: cannot open shared object file: No such file or directory



Version-Release number of selected component (if applicable):
Source install of gluster

How reproducible:
Reproducible everytime

Steps to Reproduce:
1. Start glusterd: glusterd

Actual results:
glusterd fails to start if libgfchangelog is not loaded in ldconfig

Expected results:
glusterd should not fail to start even if libgfchangelog is not loaded in ldconfig

Comment 1 Anand Avati 2014-05-09 06:52:04 UTC
REVIEW: http://review.gluster.org/7713 (geo-rep: Loading libgfchangelog.so only while running geo-rep) posted (#3) for review on master by Aravinda VK (avishwan)

Comment 2 Anand Avati 2014-05-09 07:03:31 UTC
COMMIT: http://review.gluster.org/7713 committed in master by Venky Shankar (vshankar) 
------
commit 93129e862a2dde291ddbf22fe30d955b25da6059
Author: Aravinda VK <avishwan>
Date:   Thu May 8 16:54:00 2014 +0530

    geo-rep: Loading libgfchangelog.so only while running geo-rep
    
    In source install, libgfchangelog is installed in /usr/local/lib
    When glusterd runs /usr/local/libexec/glusterfs/python/gsyncd --version
    it fails to find library without LD_LIBRARY_PATH.
    
    This patch avoids loading library when it is run from glusterd
    during start.
    
    BUG: 1096026
    Change-Id: I59912227ac27ff4877d947a7c8f1fe2e8c5be06e
    Signed-off-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/7713
    Reviewed-by: Kotresh HR <khiremat>
    Reviewed-by: Venky Shankar <vshankar>
    Tested-by: Venky Shankar <vshankar>

Comment 3 Niels de Vos 2014-09-22 12:40:04 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:32:12 UTC
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-3.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


Note You need to log in before you can comment on or make changes to this bug.