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

2009-02-16 Thread Marcelo Roccasalva
On Fri, Feb 13, 2009 at 11:09 AM, Frank Ling franklin...@yahoo.com wrote: Marcelo, I didn't see open file for /var/log/messages. Have a look at your /etc/syslog.conf -- Marcelo ¿No será acaso que ésta vida moderna está teniendo más de moderna que de vida? (Mafalda)

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

2009-02-16 Thread Frank Ling
: Re: [CentOS] logs such as messages, boot.log, and kernel contained 0 size On Fri, Feb 13, 2009 at 11:09 AM, Frank Ling franklin...@yahoo.com wrote: Marcelo, I didn't see open file for /var/log/messages. Have a look at your /etc/syslog.conf -- Marcelo ¿No será acaso que ésta vida moderna

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

2009-02-16 Thread John Doe
Frank Ling franklin...@yahoo.com *.info;*.!warn;authpriv.none;cron.nome;mail.none; -/var/log/messages I guess you alread tried to restart syslog. From the manpage: You may prefix each entry with the minus ‘‘-’’ sign to omit syncing the file after every logging. . . . Maybe try to

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

2009-02-13 Thread Marcelo Roccasalva
On Thu, Feb 12, 2009 at 11:02 PM, Frank Ling franklin...@yahoo.com wrote: Hi Marcelo, Thanks for the comment. I had SELinux disabled. Anyway I tried your trick, and it didn't work. Something must went wrong. Are the files opened?: # lsof /var/log/* Can you strace the [syslog] pid? --

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

2009-02-13 Thread Frank Ling
= Frank From: Marcelo Roccasalva marcelo-cen...@irrigacion.gov.ar To: CentOS mailing list centos@centos.org Sent: Friday, February 13, 2009 5:35:51 AM Subject: Re: [CentOS] logs such as messages, boot.log, and kernel contained 0 size

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

2009-02-12 Thread Frank Ling
centos@centos.org Sent: Wednesday, February 11, 2009 9:40:30 PM Subject: Re: [CentOS] logs such as messages, boot.log, and kernel contained 0 size 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

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

2009-02-12 Thread Marcelo Roccasalva
On Thu, Feb 12, 2009 at 1:40 AM, Jay Leafey jay.lea...@mindless.com 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

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

2009-02-12 Thread Frank Ling
Hi Marcelo, Thanks for the comment. I had SELinux disabled. Anyway I tried your trick, and it didn't work. Something must went wrong. Frank 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

[CentOS] logs such as messages, boot.log, and kernel contained 0 size

2009-02-11 Thread Frank Ling
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. The kernel is: Linux 2.6.18-92.1.22.el5 #1 SMP. Since the /var/log/messages contained no information it would be impossible to

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

2009-02-11 Thread Jay Leafey
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. The kernel is: Linux 2.6.18-92.1.22.el5 #1 SMP. Since the /var/log/messages contained no information it would be