the boot.log file is empty

deco5003 · 02-28-2010, 07:50 PM

Does anybody know why isn’t anything on the /var/log/boot.log file. After the boot I saw some services that fail to load and looking for more detail data on the boot.log file I couldn’t found anything this file is empty. This is My syslog.conf file:

Code:

kern.* /dev/console
*.info;mail.none;authpriv.none;cron.none /var/log/messages
authpriv.* /var/log/secure
authpriv.*;authpriv.!=notice /dev/console
mail.* /var/log/maillog
cron.* /var/log/cron
*.emerg *
uucp,news.crit /var/log/spooler
local7.* /var/log/boot.log

I aim using Mandriva Server 5 (MES5)

rigor · 02-28-2010, 08:36 PM

Do you look to see if you have a file named: /var/log/boot.msg

catkin · 02-28-2010, 10:21 PM

Do you know that any facility "local7" messages are being generated? If not then it is OK that /var/log/boot.msg is empty. You could try adding logger -p 'local7:notice' 'My test message' to one of the boot scripts that you are certain does run.

deco5003 · 03-01-2010, 10:52 AM

Look Thanks for the responses but I was checking that other people face the same problem. It seems to be related with bootlogd daemon. This creates the bootlogd file. Editing the file /etc/default/bootlogd and changing the variable "BOOTLOG_ENABLE" to "Yes" could resolve the problem.
But my problem is that I do not have this file. I do have /sbin/bootlogd which is the daemon. So when I try to run it /etc/init.d/bootlogd I got this error! bootlogd: cannot find console device 136:0 in /dev

Any clues Thanks

PD :The only file I have is dmesg.log this file do have info about part of the boot process mostly hardware related. But there is no info about loading services, which you usually found on boot.log file