Hide Forgot
Description of problem: When freshclam tries to install a new database, the following error is printed to STDERR (and sent to root when running freshclam-sleep from cron): ERROR: During database load : LibClamAV Warning: RWX mapping denied: Can't alloc ate RWX Memory: Permission denied Version-Release number of selected component (if applicable): clamav-0.96.5-1400.fc14.x86_64 clamav-update-0.96.5-1400.fc14.x86_64 selinux-policy-3.9.7-29.fc14.noarch How reproducible: 100 % Steps to Reproduce: 1. Install F14 with SELinux enabled, clamav, clamav-update packages 2. Comment out the "Example" line in /etc/freshclam.conf 3. Run freshclam or wait till freshclam-sleep is run by cron. Actual results: ERROR: During database load : LibClamAV Warning: RWX mapping denied: Can't alloc ate RWX Memory: Permission denied Expected results: The database should be loaded. Additional info: According to https://wwws.clamav.net/bugzilla/show_bug.cgi?id=2092, the problem is JIT-compiling the bytecode.cvd file, and then mapiing it to memory with read-write-execute permissions, which is disabled by default in Fedora kernel (I am not sure whether it is disabled in SELinux or elsewhere). Possible ways to fix the problem can be - clamav should be either compiled without JIT, - or have JIT disabled by default (in order to match the default system settings, which is RWX mappings being disallowed), - or have bytecode disabled altogether ("Bytecode no" in /etc/freshclam.conf).
To allow this on your system: setsebool -P clamd_use_jit on
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.