Re: logs such as messages, boot.log, and kernel contained 0 size

[Marcelo Roccasalva <marcelo-centos@xxxxxxxxxxxxxxxxx>]

On Thu, Feb 12, 2009 at 1:40 AM, Jay Leafey <jay.leafey@xxxxxxxxxxxx> wrote:
> Frank Ling wrote:
>>
>> Hi,
>>
>> My both CentOS 5 servers have logging problems. Logs such as messages,
>> boot.log, kernel, spooler, and tallylog in /var/log directory are all 0
>> size.
[...]
> I've had something similar happen a couple of times after an update.  In my
> case the /etc/services file got it's security context clobbered when some
> package tried to update it's contents.  When logrotate ran, the syslog
> daemon couldn't open /etc/services because of the error and I ended up with
> a bunch of empty log files.

Maybe /var/log context?

>    restorecon -R -n -v /etc

restorecon -R -n -v /var/log

You can force a global relabel:

touch /.autorelabel

and then reboot...

-- 
Marcelo

"¿No será acaso que ésta vida moderna está teniendo más de moderna que
de vida?" (Mafalda)
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos