Bug 989475

Summary:	sosreport should collect /var/run/gluster* also as it has geo-replication related log/files
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Rachana Patel <racpatel>
Component:	sos	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	amainkar
Severity:	high	Docs Contact:
Priority:	medium
Version:	2.1	CC:	asengupt, avishwan, barumuga, bmr, dblack, dkutalek, racpatel, rhs-bugs, rwheeler, vagarwal, vshankar
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-01 04:31:26 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:

Description Rachana Patel 2013-07-29 10:42:55 UTC

Description of problem:
sosreport should collect /var/run/glusterfs also as it has geo-replication related log/files

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
sosreport does not pick /var/run/gluster*

Expected results:


Additional info:

Comment 2 Bryn M. Reeves 2013-07-29 11:36:43 UTC

What sort of size are we looking at for these files? Depending on the answer it may be worth enabling either default or optional size-limits for this collection.

Comment 3 Bala.FA 2013-08-16 06:01:32 UTC

I believe /var/run is meant for daemon state file like pid.  Why logs go into /var/run/gluster* directory?

Comment 4 Venky Shankar 2013-08-16 06:36:53 UTC

(In reply to Bala.FA from comment #3)
> I believe /var/run is meant for daemon state file like pid.  Why logs go
> into /var/run/gluster* directory?

Geo-Replication uses /var/run/gluster/ as a working directory which hold processed changelogs. There is one log file generated by geo-replication (libgfchangelog.so to be precise).

I'll change that to generate log file in the standard log file directory. Collecting /var/run/gluster/ will be a good idea anyway in order to debug geo-replication changelog issues.

Comment 5 Amar Tumballi 2013-08-19 06:44:41 UTC

/var/run/gluster is for keeping any 'state' information. Ie, anything used by the process while its running. (pid is one of such state info). log here is not logging of msgs, but the 'changelog' as Venky rightly said. So please collect /var/log/gluster

Comment 6 Bryn M. Reeves 2014-06-20 10:56:50 UTC

I don't see a corresponding RHEL bug for this RFE. What's the status? It's easy enough for us to add this to sos but I'd like to see some examples of the files / directory structure that we should expect.

Comment 7 Aravinda VK 2015-01-01 04:31:26 UTC

I updated the working dir location in bz 1022523. Closing this bug as duplicate.

*** This bug has been marked as a duplicate of bug 1022523 ***