Bug 993541
Summary: | SELinux is preventing /usr/bin/perl from using the 'execmem' accesses on a process. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Robert Muil <robertmuil> |
Component: | munin | Assignee: | d. johnson <drjohnson1> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | dominick.grift, drjohnson1, dwalsh, ingvar, jvanek, kwizart, mgrepl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:90e45505d9f98eec17de9fb90bfb822ec96a696930c7be02ecd424e1d8616703 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-16 15:10:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Robert Muil
2013-08-06 07:06:28 UTC
Why does munin need execmem? This means it can write and execute the same memory, which is considered somewhat dangerous. Reporter, Can you show which plugins you are running? This is unusual for it to require execmem. Are all your graphs working, or is there one plugin's graphs that are failing? Description of problem: munin Additional info: reporter: libreport-2.1.7 hashmarkername: setroubleshoot kernel: 3.11.3-201.fc19.x86_64 type: libreport reproduced on x86_64 $ rpm -qa munin\* munin-2.0.17-6.fc19.noarch munin-common-2.0.17-6.fc19.noarch munin-node-2.0.17-6.fc19.noarch This seems to be triggered by munin-update every 5 min (so by the cron job). It would be very handy to know which plugin is causing this. Are you able to narrow down the list a bit? Which plugins do you have enabled? I've removed the nvidia driver and the error stopped, So this might be a dup of rhbz#1018083 *** This bug has been marked as a duplicate of bug 1018083 *** |