Bug 1395498

Summary:	/var/lib/glusterd/peers File had a blank line, Stopped Glusterd from starting
Product:	[Community] GlusterFS	Reporter:	Ryan Mills <ryan.mills>
Component:	glusterd	Assignee:	Gaurav Yadav <gyadav>
Status:	CLOSED EOL	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	3.8	CC:	amukherj, bugs
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1482906 1486107 (view as bug list)		Environment:
Last Closed:	2017-11-07 10:42:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1482906, 1486107

Description Ryan Mills 2016-11-16 03:23:30 UTC

Description of problem:
Basically our glusterd service would not start on Ubuntu 14.04.
Logs kept saying some old;
http://paste.ubuntu.com/23483365
Management volume was same as 7 other machines that were online in our network.

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

How reproducible:
Okay so the issue we found that in this servers /var/lib/glusterd/peers file for another server, there was a blank space line.
Whilst this existed, it would not start the service.
We have no idea where this came from suddenly, service had been working since the upgrade to 3.8.5 5 days ago.


Expected results:
If there is a commented line in these files or a blank space, it not to fail starting the service.


Additional info:
@JoeJulian advised to lodge a bug after I managed to fix it

Comment 1 Ryan Mills 2016-11-16 03:26:36 UTC

Basically when I did a 
cat /var/lib/glusterd/peers/*

It looked like this

http://paste.ubuntu.com/23483689/

Comment 2 Ryan Mills 2016-11-16 03:27:01 UTC

I changed it to look like;

uuid=01639c5d-0506-4083-b9d3-1176f2dcb912
state=3
hostname1=cb-per-04
hostname2=192.168.0.204
uuid=02c307e9-e57a-4d53-83ee-a5c768e30d6e
state=3
hostname1=cb-per-05
uuid=0dff3901-c0a4-493b-b591-a736d50bc8d3
state=3
hostname1=cb-per-07
uuid=11862aef-dbf8-423a-8056-12302aa7dfb6
state=3
hostname1=cb-per-09
uuid=12578c81-3172-4719-b86b-122f82f6be8e
state=3
hostname1=cb-per-06
uuid=62522617-7a2a-4a9f-80cc-5906272079b5
state=3
hostname1=cb-per-02
uuid=c06cdd58-ea98-46c2-aab6-b82bcbeab46a
state=3
hostname1=cb-per-03
uuid=fbf0facc-2005-48a3-8291-3f834bab3d80
state=3
hostname1=cb-per-08

Comment 3 Gaurav Yadav 2017-08-17 14:33:38 UTC

Issue is not getting reproduced after multiple trials with latest code base, hence closing the issue.

Comment 4 Atin Mukherjee 2017-08-18 05:26:35 UTC

This bug exists in all the branches, reopening it.

Comment 5 Gaurav Yadav 2017-09-07 06:11:52 UTC

upstream patch : https://review.gluster.org/18066

Comment 6 Niels de Vos 2017-11-07 10:42:53 UTC

This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.