[Bugs] [Bug 1314164] New: glusterd: does not start
bugzilla at redhat.com
bugzilla at redhat.com
Thu Mar 3 06:24:16 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1314164
Bug ID: 1314164
Summary: glusterd: does not start
Product: GlusterFS
Version: 3.7.8
Component: glusterd
Assignee: bugs at gluster.org
Reporter: amukherj at redhat.com
CC: amukherj at redhat.com, bugs at gluster.org,
mchangir at redhat.com
Depends On: 1313901
+++ This bug was initially created as a clone of Bug #1313901 +++
Description of problem:
glusterd does not start
Version-Release number of selected component (if applicable):
tested with HEAD at commit 2102010edab355ac9882eea41a46edaca8b9d02c
How reproducible:
always
Steps to Reproduce:
1.
2.
3.
Actual results:
log shows:
[2016-03-02 11:17:01.648022] D [MSGID: 0]
[glusterd-utils.c:1002:glusterd_resolve_brick] 0-management: Returning -1
Expected results:
Additional info:
Kaushal has tentatively pointed to commit a60c39de
--- Additional comment from Atin Mukherjee on 2016-03-02 23:49:30 EST ---
Please provide the reproducer steps to validate it.
--- Additional comment from Milind Changire on 2016-03-03 00:00:56 EST ---
With the latest source pull which resulted in the mentioned commit at the HEAD,
I attempted a source install. Initially glusterd started but mount was failing
throwing an ERROR log via AFR pointing to "is op-version >= 30707?". Anuradha
pointed me to a gluster-devel mail from Pranith discussing this issue. I was
advised to set cluster.op-version to 30707 ... and I did. This did not help me
get my volume mounted. So I deleted and re-created the volume and was able to
successfully mount the volume while glusterd was running in the background.
Later, I had to kill glusterd and attempted restarting it. However, this did
not succeed ... and this is the current situation.
Kaushal has done a brief source review and has some comments which might be
more helpful.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1313901
[Bug 1313901] glusterd: does not start
--
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