Bug 748930 - stat of /var/log/ceph/*.log failed: No such file or directory
Summary: stat of /var/log/ceph/*.log failed: No such file or directory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ceph
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: David Nalley
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-25 15:29 UTC by Mattia Verga
Modified: 2011-11-15 19:35 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-15 19:35:14 UTC
Type: ---


Attachments (Terms of Use)

Description Mattia Verga 2011-10-25 15:29:25 UTC
Description of problem:
Since a couple of days, logrotate gives me this error:

/etc/cron.daily/logrotate:
error: stat of /var/log/ceph/*.log failed: No such file or directory


Version-Release number of selected component (if applicable):
logrotate-3.8.0-3.fc16.x86_64
ceph-0.31-3.fc16.x86_64

Comment 1 Jan Kaluža 2011-10-26 05:20:24 UTC
Logrotate in F16 does not supress errors like it used to do in F15. This error is caused by missing "missingok" directive in ceph logrotate config file. I'm reassigning this bug to ceph maintainer.

Comment 2 Andrew McNabb 2011-10-31 21:06:44 UTC
I'm seeing this too--the emails are frustrating.

Comment 3 Andrew McNabb 2011-11-07 16:14:05 UTC
It would be really nice if this could get fixed. When Fedora 16 gets installed tomorrow, I'm going to start getting a hundred emails every day. Are there any good workarounds?

Comment 4 Josef Bacik 2011-11-07 17:19:06 UTC
I just pushed an update to testing, its ceph-0.37-1.  Let me know if it works and up the karma if it does.

Comment 5 Andrew McNabb 2011-11-07 17:29:22 UTC
Thanks. I've installed the update, and so far it looks good.

Comment 6 Mattia Verga 2011-11-08 16:40:39 UTC
I confirm, until now the problem seems to be fixed. Thank you.


Note You need to log in before you can comment on or make changes to this bug.