On Wed, 2015-07-22 at 00:50 +0530, Anand Nekkunti wrote: > Hi All > "gluster vol start" is failing when glusterfs is compiled with > debug enable . > Link: :https://bugzilla.redhat.com/show_bug.cgi?id=1245331 > > brick start is failing with fallowing error: > 2015-07-21 19:01:59.408729] I [MSGID: 100030] > [glusterfsd.c:2296:main] 0-/usr/local/sbin/glusterfsd: Started > running /usr/local/sbin/glusterfsd version 3.8dev (args: > /usr/local/sbin/glusterfsd -s 192.168.0.4 --volfile-id > VOL.192.168.0.4.tmp-BRICK1 -p > /var/lib/glusterd/vols/VOL/run/192.168.0.4-tmp-BRICK1.pid -S > /var/run/gluster/0a4faf3d8d782840484629176ecf307a.socket --brick-name > /tmp/BRICK1 -l /var/log/glusterfs/bricks/tmp-BRICK1.log --xlator > -option *-posix.glusterd-uuid=4ec09b0c-6043-40f0-bc1a-5cc312d49a78 - > -brick-port 49152 --xlator-option VOL-server.listen-port=49152) > [2015-07-21 19:02:00.075574] I [MSGID: 101190] [event > -epoll.c:627:event_dispatch_epoll_worker] 0-epoll: Started thread > with index 1 > [2015-07-21 19:02:00.078905] W [MSGID: 101095] > [xlator.c:189:xlator_dynload] 0-xlator: /usr/local/lib/libgfdb.so.0: > undefined symbol: gf_sql_str2sync_t > [2015-07-21 19:02:00.078947] E [MSGID: 101002] > [graph.y:211:volume_type] 0-parser: Volume 'VOL-changetimerecorder', > line 16: type 'features/changetimerecorder' is not valid or not found > on this machine > [2015-07-21 19:02:00.079020] E [MSGID: 101019] > [graph.y:319:volume_end] 0-parser: "type" not specified for volume > VOL-changetimerecorder > [2015-07-21 19:02:00.079150] E [MSGID: 100026] > [glusterfsd.c:2151:glusterfs_process_volfp] 0-: failed to construct > the graph > [2015-07-21 19:02:00.079399] W [glusterfsd.c:1214:cleanup_and_exit] ( > -->/usr/local/sbin/glusterfsd(mgmt_getspec_cbk+0x343) [0x40df64] - > ->/usr/local/sbin/glusterfsd(glusterfs_process_volfp+0x1a2) > [0x409b58] -->/usr/local/sbin/glusterfsd(cleanup_and_exit+0x77) > [0x407a6f] ) 0-: received signum (0), shutting down > Assuming that you are compiling with GCC v5.x, this issue is easily reproducible. 'Undefined symbol' is very possible to happen for other inline routines too. To confirm this I changed inline to static inline and re-compiled and failed to start with another routine(gf_sql_str2jm) undefined. I don't know why we don't hit this issue while glusterfs is being compiled without debug mode. > > Thanks&Regards > Anand.N > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
