Bug 1400932 - Gmond crashes when processing sflow data
Summary: Gmond crashes when processing sflow data
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ganglia
Version: 24
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Terje Røsten
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-02 10:46 UTC by Glenn L. Jenkins
Modified: 2016-12-16 03:53 UTC (History)
5 users (show)

Fixed In Version: ganglia-3.7.2-12.fc25 ganglia-3.7.2-12.fc24
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-15 23:30:15 UTC
Type: Bug


Attachments (Terms of Use)
Patch to be added to the SOURCES (636 bytes, patch)
2016-12-02 10:46 UTC, Glenn L. Jenkins
no flags Details | Diff

Description Glenn L. Jenkins 2016-12-02 10:46:30 UTC
Created attachment 1227269 [details]
Patch to be added to the SOURCES

Description of problem:

Where ganglia-gmond is used to collect data from sflow (e.g. Windows machines,) the gmond service crashes when an XML file is requested.  This can be re-created using either telnet to the listening port or gstat -a.  This results in a segmentation fault.  

This was reported as an issue in Feb on the ganglia git hub page: https://github.com/ganglia/monitor-core/issues/246

I've since submitted details of the problem and how to fix it. 

I've attached a patch file, added this to the spec file of my rpm and confirmed that the rpm built with this works as expected with sflow.  

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

ganglia-gmond-3.7.2-11

How reproducible:

Steps to Reproduce:
1. Install ganglia-gmond with default settings
2. Uncomment lines in config file to allow gmond to receive sflow packets
3. Configure another machine to send sflow data
4. Request the gmonds data in xml format, either using telent, gstat or from a gmetad collector. 

Actual results:

Segmentation fault. 

Expected results:

XML file output and the gmond keeps running. 


Additional info:

Comment 1 Glenn L. Jenkins 2016-12-05 17:01:12 UTC
This changes has been accepted on the ganglia git hub - https://github.com/ganglia/monitor-core/pull/275

Comment 2 Terje Røsten 2016-12-05 18:52:26 UTC
hi, thanks for report and fix!

Comment 3 Fedora Update System 2016-12-05 19:32:50 UTC
ganglia-3.7.2-12.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-be6fca92e9

Comment 4 Fedora Update System 2016-12-05 19:33:00 UTC
ganglia-3.7.2-12.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-b5a19c84f6

Comment 5 Fedora Update System 2016-12-07 02:26:27 UTC
ganglia-3.7.2-12.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-be6fca92e9

Comment 6 Fedora Update System 2016-12-07 02:57:35 UTC
ganglia-3.7.2-12.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b5a19c84f6

Comment 7 Fedora Update System 2016-12-15 23:30:15 UTC
ganglia-3.7.2-12.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2016-12-16 00:25:30 UTC
ganglia-3.7.2-12.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2016-12-16 03:53:06 UTC
ganglia-3.7.2-12.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.