| 2008-08-07 08:37:34 |
Matt Zimmerman |
bug |
|
|
added bug |
| 2008-08-07 08:40:02 |
Matt Zimmerman |
sysklogd: status |
New |
Confirmed |
|
| 2008-08-07 08:40:02 |
Matt Zimmerman |
sysklogd: importance |
Undecided |
High |
|
| 2008-08-07 08:40:02 |
Matt Zimmerman |
sysklogd: statusexplanation |
|
Confirmed by Martin Pitt as well. |
|
| 2008-08-07 08:40:43 |
Matt Zimmerman |
sysklogd: bugtargetdisplayname |
sysklogd (Ubuntu Intrepid) |
linux (Ubuntu Intrepid) |
|
| 2008-08-07 08:40:43 |
Matt Zimmerman |
sysklogd: bugtargetname |
sysklogd (Ubuntu Intrepid) |
linux (Ubuntu Intrepid) |
|
| 2008-08-07 08:40:43 |
Matt Zimmerman |
sysklogd: statusexplanation |
Confirmed by Martin Pitt as well. |
<pitti> mdz: hm, "sudo tail -f /proc/kmsg" doesn't report anything either (tried with some modprobe)
<pitti> itz kernel bug? |
|
| 2008-08-07 08:40:43 |
Matt Zimmerman |
sysklogd: title |
Bug #255635 in sysklogd (Ubuntu Intrepid): "Nothing logged to /var/log/kern.log in Intrepid" |
Bug #255635 in linux (Ubuntu Intrepid): "Nothing logged to /var/log/kern.log in Intrepid" |
|
| 2008-08-07 08:42:23 |
Matt Zimmerman |
description |
Binary package hint: sysklogd
On two independent systems, after upgrading from Hardy to intrepid, nothing has since been logged to /var/log/kern.log (zero bytes). This is despite several reboots and a variety of other content which is visible in dmesg. Not even the initial messages from klogd itself are logged (Inspecting /boot/System.map etc.) |
Binary package hint: sysklogd
On two independent systems, after upgrading from Hardy to intrepid, nothing has since been logged to /var/log/kern.log (zero bytes). This is despite several reboots and a variety of other content which is visible in dmesg. Not even the initial messages from klogd itself are logged (Inspecting /boot/System.map etc.)
Further inspection reveals that nothing is available for reading from /proc/kmsg |
|
| 2008-08-07 08:42:23 |
Matt Zimmerman |
title |
Nothing logged to /var/log/kern.log in Intrepid |
No messages in /proc/kmsg |
|
| 2008-08-07 08:45:30 |
Martin Pitt |
linux: status |
Confirmed |
Triaged |
|
| 2008-08-07 08:45:30 |
Martin Pitt |
linux: assignee |
|
ubuntu-kernel-team |
|
| 2008-08-07 08:45:30 |
Martin Pitt |
linux: statusexplanation |
<pitti> mdz: hm, "sudo tail -f /proc/kmsg" doesn't report anything either (tried with some modprobe)
<pitti> itz kernel bug? |
|
|
| 2008-08-13 15:14:35 |
Ben Collins |
linux: status |
Triaged |
In Progress |
|
| 2008-08-13 15:14:35 |
Ben Collins |
linux: assignee |
ubuntu-kernel-team |
ben-collins |
|
| 2008-08-13 15:14:35 |
Ben Collins |
linux: statusexplanation |
|
I've reproduced this. Working through the motions... |
|
| 2008-08-13 15:14:35 |
Ben Collins |
linux: milestone |
|
intrepid-alpha-5 |
|
| 2008-08-14 17:57:44 |
Ben Collins |
linux: status |
In Progress |
Triaged |
|
| 2008-08-14 17:57:44 |
Ben Collins |
linux: title |
Bug #255635 in linux (Ubuntu Intrepid): "No messages in /proc/kmsg" |
Bug #255635 in sysklogd (Ubuntu Intrepid): "No messages in /proc/kmsg" |
|
| 2008-08-14 17:57:44 |
Ben Collins |
linux: bugtargetname |
linux (Ubuntu Intrepid) |
sysklogd (Ubuntu Intrepid) |
|
| 2008-08-14 17:57:44 |
Ben Collins |
linux: statusexplanation |
I've reproduced this. Working through the motions... |
After more investigation, it seems that tail -f is not the right way to reproduce this. Using cat or dd shows that messages are actually getting out of /proc/kmsg. Strace shows that klogd is actually reading them, and is doing a sendto() to send them to syslog.
However, the problem is that they are not being sent to /var/log/kern.log, presumably because they are being sent as klogd.* and syslog is looking for kern.*. You can see the messages in /var/log/syslog, so it's definite that they are getting there.
Reverting back to klogd. |
|
| 2008-08-14 17:57:44 |
Ben Collins |
linux: assignee |
ben-collins |
|
|
| 2008-08-14 17:57:44 |
Ben Collins |
linux: bugtargetdisplayname |
linux (Ubuntu Intrepid) |
sysklogd (Ubuntu Intrepid) |
|
| 2008-08-15 09:07:05 |
Matt Zimmerman |
description |
Binary package hint: sysklogd
On two independent systems, after upgrading from Hardy to intrepid, nothing has since been logged to /var/log/kern.log (zero bytes). This is despite several reboots and a variety of other content which is visible in dmesg. Not even the initial messages from klogd itself are logged (Inspecting /boot/System.map etc.)
Further inspection reveals that nothing is available for reading from /proc/kmsg |
Binary package hint: sysklogd
On two independent systems, after upgrading from Hardy to intrepid, nothing has since been logged to /var/log/kern.log (zero bytes). This is despite several reboots and a variety of other content which is visible in dmesg. Not even the initial messages from klogd itself are logged (Inspecting /boot/System.map etc.)
Further inspection reveals that they are being logged to /var/log/syslog |
|
| 2008-08-15 09:07:05 |
Matt Zimmerman |
title |
No messages in /proc/kmsg |
Kernel messages not logged to /var/log/kern.log |
|
| 2008-08-15 09:07:44 |
Matt Zimmerman |
bug |
|
|
assigned to sysklogd (Debian) |
| 2008-08-15 21:33:33 |
Bug Watch Updater |
sysklogd: status |
Unknown |
New |
|
| 2008-08-30 00:40:06 |
Launchpad Janitor |
sysklogd: status |
Triaged |
Fix Released |
|
| 2008-09-02 09:04:17 |
Matt Zimmerman |
sysklogd: importance |
Unknown |
Undecided |
|
| 2008-09-02 09:04:17 |
Matt Zimmerman |
sysklogd: statusexplanation |
|
Removing the Debian bug watch; this was actually a different (Ubuntu-specific) bug |
|
| 2008-09-02 09:04:30 |
Matt Zimmerman |
sysklogd: status |
New |
Invalid |
|
| 2008-09-02 09:04:30 |
Matt Zimmerman |
sysklogd: statusexplanation |
Removing the Debian bug watch; this was actually a different (Ubuntu-specific) bug |
|
|
| 2009-06-26 23:29:11 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic/sysklogd |
|
| 2010-10-25 21:03:28 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/sysklogd |
|
