[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Logrotate: no file context?
- From: Matthew Saltzman <mjs ces clemson edu>
- To: Steve Buehler <steve ibapp com>
- Cc: "Red Hat Enterprise Linux 4 \(Nahant\) Discussion List" <nahant-list redhat com>
- Subject: Re: Logrotate: no file context?
- Date: Mon, 25 Jul 2005 11:15:00 -0400 (EDT)
On Mon, 25 Jul 2005, Steve Buehler wrote:
At 05:46 AM 7/24/2005, you wrote:
Lately, logrotate has been failing with the following error messages.
Indeed, "ls --context /var/log/*" indicates that these files have blank
contexts. How did they get that way, and how can I get them back?
Thanks.
error: error getting file context /var/log/cups/error_log: No data
available
error: error getting file context /var/log/httpd/access_log: No data
available
<----snip--->
Check your hard drive space available. One cause that your log files could
be getting emptied out is that your hard drive or partition that /var/log is
on is full. If your HD is full, when it goes to write to a file, it can end
up emptying them out instead because it can't actually write to them having
no space on the partition left. I am sure there are other reasons this could
happen too, but it happened to us on one of our machines this way in the
past.
It's not that the *files* are empty, it's that the SELinux *contexts* are
empty. There's plenty of space on the drive.
But thanks for the suggestion.
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]