| Summary: | clamav-update does not create freshclam.log with correct permissions | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Philip Prindeville <philipp> |
| Component: | clamav | Assignee: | Enrico Scholz <rh-bugzilla> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | dwalsh, mgrepl, ondrejj, philipp, pnewell0705, redhat-bugzilla, rh-bugzilla, steve |
| Target Milestone: | --- | Keywords: | SELinux |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-07-10 20:59:03 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
And... this may be a selinux issue:
[root@mail tmp]# audit2allow -m local > local.te
type=AVC msg=audit(1321481570.162:6971): avc: denied { open } for pid=31073 comm="freshclam" name="freshclam.log" dev=sda2 ino=1179679 scontext=system_u:system_r:freshclam_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:var_log_t:s0 tclass=file
[root@mail tmp]# cat local.te
module local 1.0;
require {
type var_log_t;
type freshclam_t;
class file open;
}
#============= freshclam_t ==============
allow freshclam_t var_log_t:file open;
[root@mail tmp]#
postinstall scriptlet (using /bin/sh):
test -e /var/log/freshclam.log || {
touch /var/log/freshclam.log
/bin/chmod 0664 /var/log/freshclam.log
/bin/chown root:clamupdate /var/log/freshclam.log
[-x /sbin/restorecon ] && /sbin/restorecon /var/log/freshclam.log
}
Will fix the problem.
Please fix this in F15 and F16, not sure if this effects RHEL6? clamav-0.97.3-1601.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/clamav-0.97.3-1601.fc16 Package clamav-0.97.3-1601.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing clamav-0.97.3-1601.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0334/clamav-0.97.3-1601.fc16 then log in and leave karma (feedback). clamav-0.97.3-1602.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/clamav-0.97.3-1602.fc16 (In reply to comment #6) > clamav-0.97.3-1602.fc16 has been submitted as an update for Fedora 16. > https://admin.fedoraproject.org/updates/clamav-0.97.3-1602.fc16 This should have been yanked from testing for the reasons indicated in Bohdi. See also #787434 for a still unresolved bug. clamav-0.97.5-1600.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/clamav-0.97.5-1600.fc16 clamav-0.97.5-1600.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Having done an install of clamav-update, and verified that the log file was created per the script: [root@mail ~]# rpm -q --scripts clamav-update postinstall scriptlet (using /bin/sh): test -e /var/log/freshclam.log || { touch /var/log/freshclam.log /bin/chmod 0664 /var/log/freshclam.log /bin/chown root:clamupdate /var/log/freshclam.log } [root@mail ~]# ls -ld /var/log/freshclam.log -rw-rw-r--. 1 root clamupdate 986 Nov 15 15:37 /var/log/freshclam.log [root@mail ~]# I am nonetheless seeing error messages coming back from cron via email: ERROR: Problem with internal logger (UpdateLogFile = /var/log/freshclam.log). ERROR: Can't open /var/log/freshclam.log in append mode (check permissions!). Version-Release number of selected component (if applicable): clamav-update-0.97.3-1500 How reproducible: Install clamav-update ... wait... read email. Steps to Reproduce: 1. 2. 3. Actual results: The above error messages occurs at each cron interval. Expected results: It should not be generating warnings. Additional info: