+++ This bug was initially created as a clone of Bug #1094168 +++ Description of problem: geo-rep worker dies in startup phase with following python traceback, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2014-05-05 13:39:46.172435] E [syncdutils(/bricks/master_brick1):267:log_raise_exception] <top>: FAIL: Traceback (most recent call last): File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 163, in main main_i() File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 620, in main_i local.service_loop(*[r for r in [remote] if r]) File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 1326, in service_loop g3.crawlwrap(oneshot=True) File "/usr/libexec/glusterfs/python/syncdaemon/master.py", line 501, in crawlwrap self.crawl() File "/usr/libexec/glusterfs/python/syncdaemon/master.py", line 1169, in crawl self.changelog_register_time) File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 689, in history_changelog return Changes.cl_history_changelog(changelog_path, start, end) File "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 92, in cl_history_changelog ret = cls._get_api('gf_history_changelog')(changelog_path, start, end) File "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 34, in _get_api return getattr(cls.libgfc, call) File "/usr/lib64/python2.6/ctypes/__init__.py", line 366, in __getattr__ func = self.__getitem__(name) File "/usr/lib64/python2.6/ctypes/__init__.py", line 371, in __getitem__ func = self._FuncPtr((name_or_ordinal, self)) AttributeError: /usr/lib64/libgfchangelog.so.0: undefined symbol: gf_history_changelog >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Version-Release number of selected component (if applicable): glusterfs-3.5qa2-0.425.git9360107 How reproducible: always Steps to Reproduce: 1.create and start a geo-rep relationship between master and slave. Actual results: worker dies in startup phase Expected results: It shouldn't die in startup phase. Additional info:
Upstream patches available to fix this issue 1. http://review.gluster.org/#/c/6930/ 2. http://review.gluster.org/#/c/7660/
*** This bug has been marked as a duplicate of bug 1091961 ***