[Bugs] [Bug 1215518] New: Glusterd crashed after updating to 3.8 nightly build
bugzilla at redhat.com
bugzilla at redhat.com
Mon Apr 27 05:01:27 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1215518
Bug ID: 1215518
Summary: Glusterd crashed after updating to 3.8 nightly build
Product: GlusterFS
Version: 3.7.0
Component: glusterd
Keywords: Triaged
Assignee: bugs at gluster.org
Reporter: amukherj at redhat.com
CC: bugs at gluster.org, byarlaga at redhat.com,
gluster-bugs at redhat.com, trao at redhat.com
Depends On: 1213295
Blocks: 1186580 (qe_tracker_everglades), 1199352
(glusterfs-3.7.0)
+++ This bug was initially created as a clone of Bug #1213295 +++
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.
--- Additional comment from Bhaskarakiran on 2015-04-20 05:45:29 EDT ---
Steps which i did and seen crash immediately after the gluster v start.
[root at interstellar /]# gluster v status testvol
Volume testvol is not started
[root at interstellar /]# service glusterd status
glusterd (pid 4474) is running...
[root at interstellar /]# gluster v stop testvol
Stopping volume will make its data inaccessible. Do you want to continue? (y/n)
y
volume stop: testvol: failed: Volume testvol is not in the started state
[root at interstellar /]#
[root at interstellar /]#
[root at interstellar /]# gluster v start testvol
Connection failed. Please check if gluster daemon is operational.
[root at interstellar /]# service glusterd status
glusterd dead but pid file exists
[root at interstellar /]#
--- Additional comment from Atin Mukherjee on 2015-04-20 11:25:53 EDT ---
http://review.gluster.org/#/c/10304/ is posted for review
--- Additional comment from Anand Avati on 2015-04-21 00:06:32 EDT ---
REVIEW: http://review.gluster.org/10304 (glusterd: initialize snapd svc at
volume restore path) posted (#2) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Anand Avati on 2015-04-21 00:52:25 EDT ---
REVIEW: http://review.gluster.org/10304 (glusterd: initialize snapd svc at
volume restore path) posted (#3) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Anand Avati on 2015-04-24 01:48:47 EDT ---
REVIEW: http://review.gluster.org/10304 (glusterd: initialize snapd svc at
volume restore path) posted (#4) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Kaushal on 2015-04-24 05:08:45 EDT ---
--- Additional comment from Anand Avati on 2015-04-27 00:55:03 EDT ---
COMMIT: http://review.gluster.org/10304 committed in master by Kaushal M
(kaushal at redhat.com)
------
commit 18fd2fdd60839d737ab0ac64f33a444b54bdeee4
Author: Atin Mukherjee <amukherj at redhat.com>
Date: Mon Apr 20 17:37:21 2015 +0530
glusterd: initialize snapd svc at volume restore path
In restore path snapd svc was not initialized because of which any glusterd
instance which went down and came back may have uninitialized snapd svc.
The
reason I used 'may' is because depending on the nodes in the cluster. In a
single node cluster this wouldn't be a problem since glusterd_spawn_daemon
takes
care of initializing it.
Change-Id: I2da1e419a0506d3b2742c1cf39a3b9416eb3c305
BUG: 1213295
Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-on: http://review.gluster.org/10304
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Tested-by: NetBSD Build System
Reviewed-by: Kaushal M <kaushal at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1186580
[Bug 1186580] QE tracker bug for Everglades
https://bugzilla.redhat.com/show_bug.cgi?id=1199352
[Bug 1199352] GlusterFS 3.7.0 tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1213295
[Bug 1213295] Glusterd crashed after updating to 3.8 nightly build
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list