Problem with logs.

[Erik P. Olsen]

On Mon, 2005-02-14 at 16:44 -0800, Richard E Miles wrote:
> On Tue, 15 Feb 2005 00:14:32 +0100
> "Erik P. Olsen" <erik at epo.dk> wrote:
> 
> > Some of my system logs stopped being written to on Jan 23. On that day
> > my cpu melted down and it took me about a week to recover from that and
> > I haven't noticed any missing data. But some of the logs are kept
> > untouched. The logs in question are boot.log, cron, maillog, messages,
> > mysqld.log, secure and spooler (all "spoolers" have size 0).
> > 
> > The cron daemon sent this info yesterday:
> > 
> > /etc/cron.daily/logrotate:
> > 
> > error: error getting file context /var/log/cups/access_log: No data
> > available
> > error: error getting file context /var/log/cups/error_log: No data
> > available
> > error: error getting file context /var/log/mysqld.log: No data available
> > error: error getting file context /var/log/rpmpkgs: No data available
> > error: error getting file context /var/spool/slrnpull/log: No data
> > available
> > error: error getting file context /var/log/messages: No data available
> > error: error getting file context /var/log/secure: No data available
> > error: error getting file context /var/log/maillog: No data available
> > error: error getting file context /var/log/spooler: No data available
> > error: error getting file context /var/log/boot.log: No data available
> > error: error getting file context /var/log/cron: No data available
> > error: error getting file context /var/log/up2date: No data available
> > 
> > My OS is Fedora Core 3 with all updates applied. What could possibly be
> > wrong?
> > 
> 
> Did you check to see if those files exist? If thay don't you could use the
> touch command for each one to see if this will fix your problem.
> 
Yes, they exist. That was first thing I checked :)

-- 
Regards,
Erik P. Olsen