I would like to read my Centos 5.x dmesg with timestamp, how do I do this?
-
later dmesg support the -T flag, maybe try using -T if your dmesg supports it. – ilansch Jul 24 '17 at 12:37
-
centos 7+ supports `dmesg -T` – rogerdpack Dec 21 '18 at 19:50
6 Answers
dmesg
reads the Kernel log ring buffer. It doesn't do timestamps. What you should do is configure syslog to grab the kernel logs from that buffer and send them to a file (if it isn't already set to do so). Note, default CentOS 5.x syslog config sends kernel logs to /var/log/messages
, as I recall.
If you'd like to send all kernel (dmesg) logs to /var/log/kern.log
, using the default syslog daemon, you'd add a line like the following to /etc/syslog.conf
kern.* /var/log/kern.log
- 8,999
- 2
- 31
- 43
-
4Thank you for the answer. For anyone looking that's running CentOS 6, I found it in `/etc/rsyslog.conf` – Safado Mar 30 '12 at 17:14
-
Yep, with CentOS (and RHEL) 6.x, they changed the default syslog daemon from the old sysklogd to rsyslog. It's available as a (supported) package for RHEL/CentOS 5.x, too. – Christopher Cashell Mar 30 '12 at 18:58
-
1Well, I've had this on my list of things to figure out, but now you've saved me some googling – Safado Mar 30 '12 at 22:37
There is solution "Enabling Timestamps for dmesg/Kernel Ring Buffer"
You could add:
printk.time=1
to kernel cmdline.
As for me, I have added to rc.local on all machines with puppet. It's easier for me) :
if test -f /sys/module/printk/parameters/time; then
echo 1 > /sys/module/printk/parameters/time
fi
- 103
- 2
- 91
- 1
- 2
-
-
6Using `rc.local` is really kind of an ugly solution for this (using `rc.local` is almost always an ugly solution to anything). A better solution would be to put `printk.time = 1` into `/etc/sysctl.conf` or a file in `/etc/sysctl.d/`. That's the reason these files exist. Cramming stuff into `rc.local` will eventually leave you with a fragile, convoluted, messy, unreliable start-up. – Christopher Cashell Jun 02 '14 at 22:56
-
This what is in comment from @ChristopherCashell is the only correct answer to this question. It's a shame it's not actual answer. – Petr Dec 21 '16 at 13:27
I've written this simple script. Yes, it's slow. If you want something faster you either actually write a script on perl, python or something else. I'm sure this simple script can give you the hang of how it can be calculated.
Please note I ignored the seconds fraction registered in each line (after the . in the timestamp).
#!/bin/bash
localtime() {
perl -e "print(localtime($1).\"\n\");";
}
upnow="$(cut -f1 -d"." /proc/uptime)"
upmmt="$(( $(date +%s) - ${upnow} ))"
dmesg | while read line; do
timestamp="$(echo "${line}" | sed "s/^\[ *\([0-9]\+\).*/\1/g")"
timestamp=$(( ${timestamp} + ${upmmt} ))
echo "${line}" | sed "s/^[^]]\+]\(.*\)/$(localtime "${timestamp}") -\1/g"
done
I hope it helps. :)
- 21
- 1
A little perl script as below. It's a general way, and I'm not the author.
dmesg|perl -ne 'BEGIN{$a= time()- qx!cat /proc/uptime!};s/(\d+)\.\d+/localtime($1 + $a)/e; print $_;'
perl -n
is a way to read standard input and read into variable $_.- The body (not the BEGIN section) is then run once for each line.
- BEGIN runs the code in {} once.
- $a is the start of dmesg since the epoch
- The s/... command takes the value in $_ and substitutes the #####.###### part of the timestamp with the "localtime" version of the dmesg offset ( $1) added to the system start time ($a)
- print $a prints the dmesg with the locale friendly time stamp substituted for the "seconds since boot" time stamp.
- 1,866
- 12
- 20
- 31
- 1
-
1
-
@kasperd Here is what it means: - perl -n is a way to read standard input and read into variable $_. The body (not the BEGIN section) is then run once for each line. - BEGIN runs the code in {} once. $a is the start of dmesg since the epoch - The `s/...` command takes the value in $_ and substitutes the #####.###### part of the timestamp with the "localtime" version of the dmesg offset ( $1) added to the system start time ($a). - `print $a` prints the dmesg with the locale friendly time stamp substituted for the "seconds since boot" time stamp. – dadinck Mar 28 '16 at 18:52
Script modification in case line do not begin with a "["
#!/bin/bash
localtime() {
perl -e "print(localtime($1).\"\n\");";
}
upnow=$(cut -f1 -d"." /proc/uptime)
upmmt=$(( $(date +%s) - ${upnow} ))
dmesg \
| while read LINE; do
if [ "$(echo ${LINE} | egrep -v "^\[")" == "" ] ; then
timestamp=$(echo "${LINE}" | sed "s/^\[ *\([0-9]\+\).*/\1/g")
timestamp=$(( ${timestamp} + ${upmmt} ))
echo "${LINE}" | sed "s/^[^]]\+]\(.*\)/$(localtime "${timestamp}") -\1/g"
else
echo "${LINE}"
fi
done
This is an update on Plutoid's suggestion, removing the leading spaces from the timestamp.
dmesg|perl -ne 'BEGIN{$a= time()- qx!cat /proc/uptime!};s/( *)(\d+)\.\d+/localtime($2 + $a)/e; print $_;'
- perl -n is a way to read standard input and read into variable $_.
- The body (not the BEGIN section) is then run once for each line.
- BEGIN runs the code in {} once.
- $a is the start of dmesg since the epoch (seconds)
- The s/... command takes the value in $_ and substitutes the \s*#####.###### part of the timestamp with the "localtime" version of the dmesg offset ( $1) added to the system start time ($a)
- print $a prints the dmesg with the locale friendly time stamp substituted for the "seconds since boot" time stamp.
- 1
- 2
-
1And like the original answer, it needs some explanation. Can you edit your post, break it down, and step through it? – Cory Knutson Jul 11 '17 at 20:46