[Bugs] [Bug 1213295] New: Glusterd crashed after updating to 3.8 nightly build

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1213295

            Bug ID: 1213295
           Summary: Glusterd crashed after updating to 3.8 nightly build
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: byarlaga at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Created attachment 1016274
  --> https://bugzilla.redhat.com/attachment.cgi?id=1016274&action=edit
core file of the node crashed

Description of problem:
=======================

Glusterd crashed after updating the nightly build. Here are the steps that are
done.

1. Packages are downloaded from
http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs/epel-6-x86_64/glusterfs-3.8dev-0.12.gitaa87c31.autobuild/
2. On a 4 node cluster, installed the rpms using yum install glusterfs*
3. One of the node started showing problems. It didn't list the volume when
gluster volume status <volname> is given and asked to check the service.
4. Checked with service glusterd status, it showed glusterd dead but pid
exists.
5. Tried to restart the glusterd service and stop the volume from another node
and it crashed.

Version-Release number of selected component (if applicable):
==============================================================

[root at vertigo ~]# gluster --version
glusterfs 3.8dev built on Apr 19 2015 01:13:06
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.

How reproducible:
=================
Tried once

Steps to Reproduce:
Same as in description.

Actual results:
===============
Glusterd crashed

Expected results:
=================
No crash should be seen

Additional info:
================
Attaching the corefile.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.