Gluster users - Nov 2015 - Unable to start glusterfs-server after upgrade to 3.7.6

Hi everyone,
I am using gluster for the past year with no problem. Decided to upgrade to
v3.7.6 and i couldnt start gluster ever since. this is the error im getting
> ------------------------------------------------
> glusterd --debug
> --------------------------------------------------
> [2015-11-29 16:42:43.334657] I [MSGID: 100030] [glusterfsd.c:2318:main]
> 0-glusterd: Started running glusterd version 3.7.6 (args: glusterd --debug)
> [2015-11-29 16:42:43.334713] D
> [logging.c:1790:__gf_log_inject_timer_event] 0-logging-infra: Starting
> timer now. Timeout = 120, current buf size = 5
> [2015-11-29 16:42:43.334904] D [MSGID: 0] [glusterfsd.c:638:get_volfp]
> 0-glusterfsd: loading volume file /etc/glusterfs/glusterd.vol
> [2015-11-29 16:42:43.337446] W [MSGID: 101095]
> [xlator.c:194:xlator_dynload] 0-xlator:
> /usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/xlator/mgmt/glusterd.so:
> undefined symbol: rcu_read_lock_bp
> [2015-11-29 16:42:43.337487] E [graph.y:212:volume_type] 0-parser: Volume
> 'management', line 2: type 'mgmt/glusterd' is not valid or
not found on
> this machine
> [2015-11-29 16:42:43.337526] E [graph.y:321:volume_end] 0-parser:
"type"
> not specified for volume management
> [2015-11-29 16:42:43.337547] D [graph.y:602:glusterfs_graph_construct]
> 0-parser: parsing of volfile failed, please review it once more
> [2015-11-29 16:42:43.337600] E [MSGID: 100026]
> [glusterfsd.c:2173:glusterfs_process_volfp] 0-: failed to construct the
> graph
> [2015-11-29 16:42:43.337648] D [logging.c:1764:gf_log_flush_extra_msgs]
> 0-logging-infra: Log buffer size reduced. About to flush 4 extra log
> messages
> [2015-11-29 16:42:43.337670] D [logging.c:1767:gf_log_flush_extra_msgs]
> 0-logging-infra: Just flushed 4 extra log messages
> [2015-11-29 16:42:43.337855] W [glusterfsd.c:1236:cleanup_and_exit]
> (-->glusterd(glusterfs_volumes_init+0xcd) [0x7fb5893a983d]
> -->glusterd(glusterfs_process_volfp+0x126) [0x7fb5893a9716]
> -->glusterd(cleanup_and_exit+0x71) [0x7fb5893a8d41] ) 0-: received
signum
> (0), shutting down
> [2015-11-29 16:42:43.337894] D
> [glusterfsd-mgmt.c:2268:glusterfs_mgmt_pmap_signout] 0-fsd-mgmt: portmapper
> signout arguments not given

These are the steps i took to upgrade

wget -O -
> http://download.gluster.org/pub/gluster/glusterfs/3.7/3.7.6/pub.key |
> sudo apt-key add -
> sudo sh -c "echo 'deb
>
http://download.gluster.org/pub/gluster/glusterfs/3.7/3.7.6/Debian/wheezy/apt
> wheezy main' > /etc/apt/sources.list.d/gluster.list "
>  sudo apt-get update
>  sudo apt-get install glusterfs-server

Im unable to install the glusterfs-server completely and im unable to start
the service manually..

This is my glusterd.vol

volume management
     type mgmt/glusterd
     option working-directory /var/lib/glusterd
     option transport-type socket,rdma
     option transport.socket.keepalive-time 10
     option transport.socket.keepalive-interval 2
     option transport.socket.read-fail-log off
end-volume

Its the same as the old ones....
Please help!!

Thanks,
Kaamesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20151130/061cdaf7/attachment.html>

Hi Kaamesh,

Le 29/11/2015 17:57, Kaamesh Kamalaaharan a ?crit :
> Hi everyone,
> I am using gluster for the past year with no problem. Decided to 
> upgrade to v3.7.6 and i couldnt start gluster ever since. this is the 
> error im getting
I manage two glusterfs :

  * one with 14 nodes and two volumes around 500To ;
  * the other with four nodes with also two volumes  with  To ;

I work with the 3.6.6 released.  Why ?

I have tested one day the 7.x release and encounter many problems as 
you. That doesn't means that the 3.7.x track is bad,  that means the 
theses releases are  a test releases ans need more attention, that the 
stable releases.


My opinion,  is that I will work always with the 3.6.6 release, still 
the 3.8.x which is announced as a more reliable release.
And the I will build numerous VM with that release to work on the 
configuration differences before put them in production.

I think that it's the more fluently approach of a such complex system.

Sincerely

Pierre L?onard

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20151129/ba6cd534/attachment.html>

----- Original Message -----
> From: "Kaamesh Kamalaaharan" <kaamesh at novocraft.com>
> To: gluster-users at gluster.org
> Sent: Sunday, November 29, 2015 11:57:37 AM
> Subject: [Gluster-users] Unable to start glusterfs-server after upgrade to
3.7.6
> 
> Hi everyone,
> I am using gluster for the past year with no problem. Decided to upgrade to
> v3.7.6 and i couldnt start gluster ever since. this is the error im getting
> 
> 
> ------------------------------------------------
> glusterd --debug
> --------------------------------------------------
> [2015-11-29 16:42:43.334657] I [MSGID: 100030] [glusterfsd.c:2318:main]
> 0-glusterd: Started running glusterd version 3.7.6 (args: glusterd --debug)
> [2015-11-29 16:42:43.334713] D [logging.c:1790:__gf_log_inject_timer_event]
> 0-logging-infra: Starting timer now. Timeout = 120, current buf size = 5
> [2015-11-29 16:42:43.334904] D [MSGID: 0] [glusterfsd.c:638:get_volfp]
> 0-glusterfsd: loading volume file /etc/glusterfs/glusterd.vol
> [2015-11-29 16:42:43.337446] W [MSGID: 101095]
[xlator.c:194:xlator_dynload]
> 0-xlator:
/usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/xlator/mgmt/glusterd.so:
> undefined symbol: rcu_read_lock_bp

This seems to indicate that liburcu package is not installed or not available in
the loader's path. Can you please verify if that is the case?

Regards,
Vijay