Bug 867503
| Summary: | Munin uses perl -T, but doesn't require the perl-Taint-Runtime package | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael <vendor-redhat> |
| Component: | munin | Assignee: | Kevin Fenzi <kevin> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | drjohnson1, ingvar, jvanek, kevin, netllama, pdx |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-11-28 05:06:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Michael
2012-10-17 15:50:03 UTC
dupe of Bug 867437? They could be combined into a single ticket. I searched prior to submitting, but didn't find anything on this. There are two issues. One, passing additional arguments to perl via env and the second is making sure perl-Taint-Runtime is installed. I don't believe issue 867437 would directly address the second issue. Installing perl-Taint-Runtime doesn't seem to fix the cronjob errors though. It fixed it for me. Make sure you completely stop and restart munin. Can you now run perl -T without it complaining about uknown options? I thought munin (not munin-node) was cron driven? Regardless, its a cronjob that is failing, so I'm not sure what I'd restart. Specifically what did you stop & restart? confirming error. it resulted in my munin installation actually working, but not producing any images (and munin-graph.log was empty), and my root inbox filled quickly with mail describing the error above. for now, i've fixed it using a patch found for pipermail: http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-January/029373.html i.e. removed the -T argument from munin-graph's first line, and it works without a glitch. but the env+perl args issue hints at something bigger and possibly much more problematic. i guess that's an issue that should be resolved ASAP. be advised: bind9 plugin dies similarly; env and the -w switch don't play well together. remind me again, why are we using the env now? In one of the other numerous munin buzilla bugs associated with the 2.0.7 update, someone commented that Fedora is basically just repackaging what comes from upstream, and not making any functional changes (or enhancements). If that's true, then this came from upstream. No clue why the change was made though. Andras, because the upstream tarball has it .. The new packages will not. Lonni, correct. It came from upstream. koji has a 2.0.7-2 build if you want, or 2.0.7-3 will be coming out shortly with this and a few other minor fixes. The -3 release will be in -testing first. Please feel free to check there and report. Can you post the URL(s) for the 2.0.7-3 koji builds (once available)? I'll be happy to test them out. munin-2.0.7-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/munin-2.0.7-3.fc16 munin-2.0.7-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/munin-2.0.7-3.fc17 munin-2.0.7-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/munin-2.0.7-3.fc18 munin-2.0.7-3.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/munin-2.0.7-3.el5 munin-2.0.7-3.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/munin-2.0.7-3.el6 Package munin-2.0.7-3.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 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.7-3.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-13237/munin-2.0.7-3.el5 then log in and leave karma (feedback). These 2.0.7-3 RPMs, appear to be shipping /var/lib/munin/state-phx2.fedoraproject.org-buildvm-33.phx2.fedoraproject.org.storable Is that intended? nice catch Lonni. will update the spec once i find why it was included. Aside from that, the original issue: /usr/bin/env: perl -T: No such file or directory Has it been resolved with this update? Yes, the cronjob failures are no longer present. thanks munin-2.0.7-5.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/munin-2.0.7-5.el6 munin-2.0.7-5.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/munin-2.0.7-5.el5 munin-2.0.8-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/munin-2.0.8-1.el6 munin-2.0.8-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/munin-2.0.8-1.el5 munin-2.0.8-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. munin-2.0.8-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. |