Problem with logs.

Erik P. Olsen erik at epo.dk
Mon Feb 14 23:14:32 UTC 2005


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?

-- 
Regards,
Erik P. Olsen




More information about the fedora-list mailing list