imklog: cannot open kernel log (/proc/kmsg): No such file or directory

[steowens]

Expected behavior

rsyslog starts and does not emit the error with text to syslog:
rsyslogd: imklog: cannot open kernel log (/proc/kmsg): No such file or directory.

Actual behavior

rsyslog starts and emits the error with text to syslog:
rsyslogd: imklog: cannot open kernel log (/proc/kmsg): No such file or directory.

Steps to reproduce the behavior

On Windows 10 enable Windows Linux Subsystem WSL.
Start a bash console, by entering bash in the run bar and then selecting bash.

Enter the following commands:
sudo -i
apt-get update
apt-get install rsyslog
service rsyslog start
tail -f /var/log/syslog

Environment

• rsyslog version: 8.16.0
• platform: Linux LAPTOP-OT0BG026 4.4.0-43-Microsoft Various fixes in GT signing #1-Microsoft Wed Dec 31 14:42:53 PST 2014 x86_64 x86_64 x86_64 GNU/Linux
• for configuration questions/issues, include rsyslog.conf:

Note: rsyslog documentation is available here:
pre-release,
current stable release

[rgerhards]

It looks like the Windows Subsystem does not provide a kernel log, or maybe you do not have permissions to read it.

Can you do a sudo cat /proc/kmsg and report what happens?

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.