boot.log contaminated

[redesb]

Hi,

While it examined logs of the server (CentOS 4.3), I have found these strange entrances in the boot.log file:
Aug 6 04:25:19 exp3 xinetd: xinetd shutdown succeeded
Aug 6 04:25:19 exp3 xinetd: xinetd startup succeeded
...
Aug 8 20:45:41 exp3 sshd: sshd -TERM succeeded
Aug 8 20:45:41 exp3 sshd: succeeded
...
Aug 9 00:11:01 exp3 httpd: httpd shutdown succeeded
Aug 9 00:11:01 exp3 httpd: [Wed Aug 9 00:11:01 2006] [warn] NameVirtualHost 1.2.3.4:80 has no VirtualHosts
Aug 9 00:11:01 exp3 httpd:
Aug 9 00:11:01 exp3 httpd: [Wed Aug 9 00:11:01 2006] [warn] NameVirtualHost 1.2.3.4:443 has no VirtualHosts
Aug 9 00:11:01 exp3 httpd: httpd startup succeeded
Aug 9 03:00:30 exp3 named: named shutdown succeeded
Aug 9 03:00:30 exp3 named: named startup succeeded
Aug 10 00:11:01 exp3 httpd: httpd shutdown succeeded
Aug 10 00:11:01 exp3 httpd: [Thu Aug 10 00:11:01 2006] [warn] NameVirtualHost 1.2.3.4:80 has no VirtualHosts
Aug 10 00:11:01 exp3 httpd:
Aug 10 00:11:01 exp3 httpd: [Thu Aug 10 00:11:01 2006] [warn] NameVirtualHost 1.2.3.4:443 has no VirtualHosts
Aug 10 00:11:02 exp3 httpd: httpd startup succeeded
Aug 11 00:11:02 exp3 httpd: httpd shutdown succeeded
Aug 11 00:11:02 exp3 httpd: [Fri Aug 11 00:11:02 2006] [warn] NameVirtualHost 1.2.3.4:80 has no VirtualHosts
Aug 11 00:11:02 exp3 httpd:
Aug 11 00:11:02 exp3 httpd: [Fri Aug 11 00:11:02 2006] [warn] NameVirtualHost 1.2.3.4:443 has no VirtualHosts
Aug 11 00:11:03 exp3 httpd: httpd startup succeededI have thought that can be an error of configuration of syslog.conf file but seems to me correct, see bellow:
# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.* /dev/console
# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none /var/log/messages
# The authpriv file has restricted access.
authpriv.* /var/log/secure
# Log all the mail messages in one place.
mail.* -/var/log/maillog
# Log cron stuff
cron.* /var/log/cron
# Everybody gets emergency messages
*.emerg *
# Save news errors of level crit and higher in a special file.
uucp,news.crit /var/log/spooler
# Save boot messages also to boot.log
local7.* /var/log/boot.log
This happens in all the servers who I have with CentOS 4,3 and I do not believe that it is related to the Control Panel then in that I have with Plesk, happens the same.

Somebody has the same problem?
Some suggestion to solve it?

TIA
Ramon

[jlasman]

If it's a CentOS issue, then the best place to discuss it would be a CentOS forum.

Of course they'll just tell you that they slavishly copy whatever Red Hat does, so the best place to discuss it may be a Red Hat forum.

Jeff

[redesb]

Thanks Jeff for your comments, but I find nothing in centos/redhat forums, however, after rereading the manuals of klogd and syslogd, I have found out the reason that these entrances are in the boot.log file.

The line of syslog.conflocal7.* /var/log/boot.log specifies that any message of kernel below level 7 (level of debug) keeps in the boot.log file, that is to say, any message that the system sends to /dev/console, finishes in boot.log.

Pardon by the false alarm.

Greetings,
Ramon

[jlasman]

I never thought of it as an alarm. I was referring you to a forum where you could discuss why the distribution chose that particular logging scheme :) .

Jeff