I'm looking for causes of a particular problem in kern.log. There are many entries with a 00:00:00 timestamp:
Jun 11 00:00:00 mymachine kernel: [ 0.000000] Initializing cgroup subsys cpusetJun 11 00:00:00 mymachine kernel: [ 0.000000] Initializing cgroup subsys cpu Jun 11 00:00:00 mymachine kernel: [ 0.000000] Linux version 3.2.0-33-virtual (buildd@batsu) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #52-Ubuntu SMP Thu Oct 18 16:48:3 7 UTC 2012 (Ubuntu 3.2.0-33.52-virtual 3.2.31) Jun 11 00:00:00 mymachine kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-33-virtual root=LABEL=cloudimg-rootfs ro console=ttyS0
Assuming I didn't actually boot the machine up at midnight - does the 00:00:00 timestamp mean a particular phase of the bootup process? Any particular reason they do this?
(It's an Ubuntu Precise VM hosted on OpenStack, if that matters. I think this boot up was immediately after being cloned from another image.)
EDIT More information:
As far as I can tell (
ls /etc/ntp* ) ntp is not running.
The time seems to (correctly) be set to UTC, with (incorrectly) no local timezone set.
EDIT2 The last log entries at 00:00:00 looks like this:
Jun 11 00:00:00 mymachine kernel: [ 6.324599] type=1400 audit(1370908796.761:11): apparmor="STATUS" operation="profile_load" name="/usr/sbin/tcpdump" pid=875 comm="apparmor_parser" Jun 11 00:00:02 mymachine kernel: [ 12.259133] postgres (1033): /proc/1033/oom_adj is deprecated, please use /proc/1033/oom_score_adj instead. Jun 11 00:00:05 mymachine kernel: [ 13.592385] eth0: no IPv6 routers present Jun 11 06:22:15 mymachine kernel: [22942.768233] init: tilemill main process (3167) killed by TERM signal Jun 11 06:40:14 mymachine kernel: [24022.599001] init: tilemill main process (5640) killed by TERM signal