Bug 1091219 - Graphing subgroups stopped working in 2.0.20
Summary: Graphing subgroups stopped working in 2.0.20
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: munin
Version: el6
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: d. johnson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-25 08:44 UTC by nrm
Modified: 2014-06-14 20:01 UTC (History)
2 users (show)

Fixed In Version: munin-2.0.21-1.el5
Clone Of:
Environment:
Last Closed: 2014-05-06 03:33:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description nrm 2014-04-25 08:44:46 UTC
Description of problem:
After upgrading from 2.0.19 to 2.0.20 the graphing of subgroups has stopped working.

Downgrading to 2.0.19 fixes the problem. 

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

How reproducible:
Always

Steps to Reproduce:
1. Upgrade to 2.0.20
2. Have subgroups in munin.conf

Actual results:

yum.log
=======
Dec 24 05:26:14 Updated: munin-2.0.19-1.el6.noarch
Apr 16 06:31:00 Updated: munin-2.0.20-1.el6.noarch

munin.conf
==========
[calx;001-019;calx001.ast.cam.ac.uk]
        address calx001.ast.cam.ac.uk

munin log
=========
2014/04/16 06:31:40 [RRD ERROR] Unable to graph /export/munin/html/calx/001-019/calx001.ast.cam.ac.uk/cpu-day.png : opening '/export/munin/db/calx/001-019-calx001.ast.cam.ac.uk-cpu-guest-d.rrd': No such file or directory
2014/04/16 06:31:40 [RRD ERROR] rrdtool 'graph' '/export/munin/html/calx/001-019/calx001.ast.cam.ac.uk/cpu-day.png' \

Expected results:
Graphing continues to work

Additional info:

Discussion on munin mailing list here:

http://sourceforge.net/p/munin/mailman/munin-users/thread/53562D43.70108%40mines-paristech.fr/#msg32254031

I believe this has been fixed in 2.0.21, is it possible to get this into EPEL 6? 

Thanks.

Comment 1 Fedora Update System 2014-04-26 01:18:04 UTC
munin-2.0.21-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/munin-2.0.21-1.fc20

Comment 2 Fedora Update System 2014-04-26 01:19:42 UTC
munin-2.0.21-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/munin-2.0.21-1.fc19

Comment 3 Fedora Update System 2014-04-26 01:24:16 UTC
munin-2.0.21-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/munin-2.0.21-1.el6

Comment 4 Fedora Update System 2014-04-26 01:24:56 UTC
munin-2.0.21-1.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/munin-2.0.21-1.el5

Comment 5 Fedora Update System 2014-04-26 20:11:10 UTC
Package munin-2.0.21-1.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing munin-2.0.21-1.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1249/munin-2.0.21-1.el6
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-05-06 03:33:51 UTC
munin-2.0.21-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2014-05-06 03:40:06 UTC
munin-2.0.21-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 nrm 2014-06-13 13:54:22 UTC
Hi,

Is it possible to get this pushed from EPEL 6 testing to stable?

Thanks,
Neil.

Comment 9 Fedora Update System 2014-06-14 20:01:21 UTC
munin-2.0.21-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2014-06-14 20:01:28 UTC
munin-2.0.21-1.el5 has been pushed to the Fedora EPEL 5 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.