Bug #7168
closed
Vague kernel messages in system log
0%
Description
I'm running the a recent 2.4 beta snapshot. I'm periodically seeing vague kernel messages in the system log.
Some examples are shown below (e.g., kernel done., kernel .done., kernel ..). Log messages can be useful, but these are just clutter. It's not a show stopper to have these messages, but if a message is going to be logged, it should at least contain useful information.
Jan 28 13:18:44 kernel done.
Jan 28 13:18:44 php-fpm 37361 /rc.start_packages: Restarting/Starting all packages.
Jan 28 13:18:44 syslogd kernel boot file is /boot/kernel/kernel
Jan 28 13:18:44 syslogd exiting on signal 15
Jan 28 13:18:44 kernel done.
Jan 28 13:18:44 php-cgi rc.bootup: Creating rrd update script
Jan 28 13:18:39 kernel .done.
Jan 28 13:18:39 kernel ..
Jan 28 13:18:39 kernel ..
Jan 28 13:18:39 check_reload_status Updating all dyndns
Jan 28 13:18:39 kernel done.
Jan 28 13:18:38 kernel done.
Jan 28 13:18:38 php-cgi rc.bootup: NTPD is starting up.
Jan 28 13:18:38 kernel done.
Jan 28 13:18:37 kernel done.
Updated by → luckman212 about 7 years ago
Noticed the same thing - have not seen them before. Running 2.4 snap 2.4.0.b.20170213.0512
Feb 13 07:46:33 r1 kernel: . Feb 13 07:46:33 r1 kernel: . Feb 13 07:46:33 r1 kernel: .. Feb 13 07:46:34 r1 php-cgi: rc.bootup: Removing static route for monitor 68.237.161.12 and adding a new route through 173.56.90.1 Feb 13 07:46:34 r1 kernel: .done. Feb 13 07:46:34 r1 php-cgi: rc.bootup: Removing static route for monitor 2001:4860:4860::8888 and adding a new route through fe80::217:10ff:fe88:498d%igb2 Feb 13 07:46:34 r1 php-cgi: rc.bootup: Removing static route for monitor 24.29.99.36 and adding a new route through 74.66.0.1 Feb 13 07:46:34 r1 php-cgi: rc.bootup: Removing static route for monitor 8.8.4.4 and adding a new route through 10.8.8.73 Feb 13 07:46:34 r1 kernel: done. Feb 13 07:46:34 r1 php-cgi: rc.bootup: ROUTING: setting default route to 173.56.90.1 Feb 13 07:46:34 r1 php-cgi: rc.bootup: ROUTING: setting IPv6 default route to fe80::217:10ff:fe88:498d%igb2 Feb 13 07:46:35 r1 kernel: done. Feb 13 07:46:36 r1 kernel: done. Feb 13 07:46:37 r1 kernel: done. Feb 13 07:46:37 r1 php-cgi: rc.bootup: NTPD is starting up. Feb 13 07:46:37 r1 kernel: done. Feb 13 07:46:37 r1 kernel: done. Feb 13 07:46:37 r1 kernel: done. Feb 13 07:46:38 r1 check_reload_status: Updating all dyndns Feb 13 07:46:41 r1 kernel: . Feb 13 07:46:41 r1 kernel: . Feb 13 07:46:41 r1 kernel: .. Feb 13 07:46:42 r1 kernel: .done.
Updated by Phillip Davis about 7 years ago
The 'done' and the dots are output by steps of the boot script as it gets to various points in the code. That comes out on the console during boot. I guess that console output is being periodically flushed into the log by some new setting.
Updated by Daryl Morse about 7 years ago
Phillip Davis wrote:
The 'done' and the dots are output by steps of the boot script as it gets to various points in the code. That comes out on the console during boot. I guess that console output is being periodically flushed into the log by some new setting.
I realize this isn't a big deal and since these messages pertain to the kernel so this may be an upstream issue, but if someone is going to go to the effort of logging something, the log entry should be at least be descriptive enough to be useful for troubleshooting. As they are, these messages are completely useless clutter.
Updated by Jim Pingle over 4 years ago
- Category set to Operating System
- Status changed from New to Closed
This still happens but there isn't much we can do about it, and even if we could, I'm not sure it would be helpful. The log entries are output from the kernel message buffer indicating progress. So taken alone they may appear vague but in context they give admins an idea about how the boot process is progressing.