Bug 12085 - logrotate doesn't succeed because of lose permission
Summary: logrotate doesn't succeed because of lose permission
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Spuhler
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 11288
Blocks:
  Show dependency tree / graph
 
Reported: 2013-12-22 21:28 CET by Thomas Spuhler
Modified: 2014-01-23 17:05 CET (History)
0 users

See Also:
Source RPM: clamav-0.98-1
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Thomas Spuhler 2013-12-22 21:28:08 CET 
Description of problem:
logrotate[26941]: error: skipping "/var/log/clamav/clamd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
Dec 22 04:02:05 vbox.btspuhler.com logrotate[26941]: error: skipping "/var/log/clamav/freshclam.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

Version-Release number of selected component (if applicable):

0.98-1

How reproducible:
every weekend when log getting rotated by cron

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Thomas Spuhler 2013-12-22 21:29:56 CET 
version clamav-0.98-1.2 in updates_testing should solves this issue. I will get this tested next weekend.

Status: NEW => ASSIGNED

Comment 2 Manuel Hiebel 2013-12-23 10:16:52 CET 
btw maybe you can inform QA now as there was one in test: https://bugs.mageia.org/show_bug.cgi?id=11288
Thierry Vignaud 2013-12-26 19:31:53 CET

Summary: logrotate doesn succeed because of lose permission => logrotate doesn't succeed because of lose permission

Comment 3 Thomas Spuhler 2014-01-16 03:23:18 CET 
this bug seems to be solved now. I haven't seen it anymore.
I am going to assign this now to QA so it can be taken care of together with bug #11288 as listed in Comment 2

Assignee: bugsquad => qa-bugs

claire robinson 2014-01-16 08:00:49 CET

Assignee: qa-bugs => thomas
Blocks: (none) => 11288

Comment 4 Thomas Spuhler 2014-01-16 18:16:36 CET 
version clamav-0.98-1.2 is in updates_testing.
you can test this by changing the date of the system into the next month and run 
/usr/sbin/logrotate -v /etc/logrotate.conf as root
There shouldn't be any error in the clamd/clamav section( the first logrotate section)

Updated packages in {core,tainted}/updates_testing:
========================
clamav-0.98-1.2.mga3.src.rpm
lib64clamav6-0.98-1.2.mga3
clamd-0.98-1.2.mga3
clamav-db-0.98-1.2.mga3
clamav-0.98-1.2.mga3
clamav-milter-0.98-1.2.mga3
lib64clamav-devel-0.98-1.2.mga3
clamav-debuginfo-0.98-1.2.mga3
David Walser 2014-01-16 22:58:13 CET

Depends on: (none) => 11288
Blocks: 11288 => (none)

Comment 5 Thomas Spuhler 2014-01-23 17:05:52 CET 
This has now been taken care of with version 0.98.1-1

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.