Gluster users - Oct 2015 - glusterd crashing

Happy to do so... what all info should go in the bug report?





--
*Gene Liverman*
Systems Integration Architect
Information Technology Services
University of West Georgia
gliverma at westga.edu
678.839.5492

ITS: Making Technology Work for You!




On Thu, Oct 8, 2015 at 1:04 PM, Vijay Bellur <vbellur at redhat.com>
wrote:
> On Wednesday 07 October 2015 09:20 PM, Atin Mukherjee wrote:
>
>> This looks like a glibc corruption to me. Which distribution platform
>> are you running Gluster on?
>>
>>
> A crash in glibc would mostly be due to memory corruption caused by the
> application. Can we please open a tracking bug if not done yet?
>
> Thanks,
> Vijay
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20151008/ad28be2e/attachment.html>

On Thursday 08 October 2015 11:01 PM, Gene Liverman
wrote:
> Happy to do so... what all info should go in the bug report?
>
Guidelines for logging a bug are available at [1]. Please try to provide 
relevant data requested in the Package Information, Cluster Information, 
Volume Information and Logs section of the guidelines page. Information 
pertaining to bricks, volume details & statedump can be skipped as it is 
the management daemon that is crashing here. Attaching the entire 
glusterd log would be helpful.

Regards,
Vijay

[1] 
http://www.gluster.org/community/documentation/index.php/Bug_reporting_guidelines