Bug 987761

Summary: Segmentation fault during cf-monitord start
Product: [Fedora] Fedora Reporter: Richard Neuboeck <hawk>
Component: cfengineAssignee: Christopher Meng <i>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 19CC: nick, ravenoak, sheltren
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-18 14:02:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Richard Neuboeck 2013-07-24 06:19:54 UTC
Description of problem:
cf-monitord does not start because a segmentation fault occurs

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

How reproducible:
On all x86_64 machines I've tested.

Steps to Reproduce:
1. Install cfengine-3.3.0-3.fc19.x86_64
2. Run cf-monitord as root

Actual results:
Trying to start cf-monitord fails with a seg fault:

# cf-monitord
Segmentation fault

Expected results:
A running cf-monitord in the background

Additional info:
I've used gdb and found that the function 'MonitorInitialize' in src/env_monitor.c failes to initialize the array HISTOGRAM[i][j][k] due to mixed up variables.

HISTOGRAM is defined as:


But initialized as follows. The upper limit of i should be CF_OBSERVABLES and of j it should be 7:

    for (i = 0; i < 7; i++)
        for (j = 0; j < CF_OBSERVABLES; j++)
            for (k = 0; k < CF_GRAINS; k++)
                HISTOGRAM[i][j][k] = 0;

However, the most confusing thing is that simply downloading the corresponding src.rpm and rebuilding it seems to overcome the seg fault problem though the sources clearly have the same mixed up variables.

Comment 1 Fedora Admin XMLRPC Client 2013-09-16 08:49:51 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Christopher Meng 2013-09-17 01:38:50 UTC
I will push an update of 3.5.2 later, can you help test it?

Comment 3 Richard Neuboeck 2013-09-17 05:16:36 UTC
(In reply to Christopher Meng from comment #2)
> I will push an update of 3.5.2 later, can you help test it?

Nö problem. Give me package and I'll test it tomorrow morning.

Comment 4 Fedora End Of Life 2015-01-09 22:13:19 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-02-18 14:02:00 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.