Skip to content

Instantly share code, notes, and snippets.

@0x49D1

0x49D1/syslog_wsl_windows10_problem.md

Created November 15, 2019 12:03
Show Gist options
  • Star 3 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save 0x49D1/596d457921034e9c18e5e1052a4ad515 to your computer and use it in GitHub Desktop.
Save 0x49D1/596d457921034e9c18e5e1052a4ad515 to your computer and use it in GitHub Desktop.
Download ZIP
rsyslog restart problem in WSL. No syslog logs in /var/log
Raw
syslog_wsl_windows10_problem.md

Windows version: Windows 10 Pro 1909 Command: sudo service rsyslog restart

  • Stopping enhanced syslogd rsyslogd [ OK ]
  • Starting enhanced syslogd rsyslogd rsyslogd: set SO_TIMESTAMP failed on '/dev/log': Invalid argument [v8.32.0] rsyslogd: imklog: cannot open kernel log (/proc/kmsg): No such file or directory.
    rsyslogd: activation of module imklog failed [v8.32.0 try http://www.rsyslog.com/e/2145 ]

Solution:
https://askubuntu.com/questions/615457/no-logs-are-written-to-var-log/615473
sudo apt-get install --reinstall rsyslog
And start after that! restart is not working.
sudo service rsyslog restart

  • Starting enhanced syslogd rsyslogd [ OK ]
@fuhrmanator
Copy link

Strange, I get the same error even after that solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment