Bug 834355 - cacti rpm from epel-testing is missing plugins/ directory (upstream bug 0002221)
Summary: cacti rpm from epel-testing is missing plugins/ directory (upstream bug 0002221)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: cacti
Version: el6
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ken Dreyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-21 15:56 UTC by giovanni.torres
Modified: 2013-01-16 21:22 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-16 21:22:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description giovanni.torres 2012-06-21 15:56:43 UTC
Description of problem:
Upstream bug 0002221 is present in the latest epel-testing cacti rpm.  The rpm does not create the $base_path/plugins/ directory.  The Plugin Architecture is now built in to cacti 0.8.8.  When you click the Plugin Architecture link inside the console, it endlessly logs the follow to the appropriate httpd error log:

"httpd: PHP Warning: readdir() expects parameter 1 to be resource, boolean given in /var/www/cacti/plugins.php on line 277"

Version-Release number of selected component (if applicable):
cacti-0.8.8-3.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. yum --enablerepo=epel-testing install cacti
2. once installed, click the Console tab at the top of the page
3. click Plugin Management under the Configuration section on the left navigation bar.
4. tail -f /var/log/httpd/error_log
  
Actual results:
1. /usr/share/cacti/plugins is missing after installing cacti rpm
2. endless loop of error messages in httpd error log
3. the plugins.php page shows no output


Expected results:
1. /usr/share/cacti/plugins exists after installing cacti rpm
2. no error messages in httpd error log
3. the plugins.php should display the current plugin management configuration
 

Additional info:
This bug is resolved in upstream bug 0002221 (http://bugs.cacti.net/view.php?id=2221).  They ask to notify the maintainer, so I filled out a bug report here.

Comment 1 Ken Dreyer 2012-06-28 13:29:14 UTC
First, let me say *thank you* for testing the epel-testing package, and providing feedback!

0.8.8a has been in Fedora for a month, and I'm going to just go ahead and push that out to EPEL, along with a fix for this.

Would you mind trying out this Koji scratch build, and letting me know how this works for you? http://koji.fedoraproject.org/koji/taskinfo?taskID=4204894

Comment 2 Ken Dreyer 2012-06-28 14:01:20 UTC
EL-5 scratch build at http://koji.fedoraproject.org/koji/taskinfo?taskID=4204997

Seems to fix the issue for me on my systems.

Comment 3 Fedora Update System 2012-06-28 14:17:08 UTC
cacti-0.8.8a-2.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-0986/cacti-0.8.8a-2.el6

Comment 4 Fedora Update System 2012-06-28 14:18:55 UTC
cacti-0.8.8a-2.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-0990/cacti-0.8.8a-2.el5

Comment 5 giovanni.torres 2012-06-28 19:27:41 UTC
http://koji.fedoraproject.org/koji/taskinfo?taskID=4204894

Fixed on EL6 for me.  plugins/ directory is installed by default and the plugins page works as expected. Thanks!

Comment 6 Ken Dreyer 2012-06-29 12:57:58 UTC
(In reply to comment #5)
> http://koji.fedoraproject.org/koji/taskinfo?taskID=4204894
> 
> Fixed on EL6 for me.  plugins/ directory is installed by default and the
> plugins page works as expected. Thanks!

Very cool. Do you have a Fedora account? You can add Karma at the link in Comment 3

Comment 7 Fedora Update System 2012-08-10 18:36:28 UTC
cacti-0.8.8a-2.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 8 Fedora Update System 2012-08-10 18:38:51 UTC
cacti-0.8.8a-2.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.