Am 04.09.2014 23:07, schrieb Vedran Furač: > # logger -t TEST 1234 > # tail -1 /var/log/syslog > Sep 4 22:38:09 hostname rsyslogd: [origin software="rsyslogd" > swVersion="8.4.0" x-pid="2886" x-info="http://www.rsyslog.com";] exiting > on signal 15. > > # journalctl --system|tail -1 > Ruj 04 22:40:13 rigel TEST[2957]: 1234 > > # systemctl status syslog.socket rsyslog.service > > ● syslog.socket - Syslog Socket > Loaded: loaded (/lib/systemd/system/syslog.socket; static) > Active: inactive (dead) > Docs: man:systemd.special(7) > http://www.freedesktop.org/wiki/Software/systemd/syslog > Listen: /run/systemd/journal/syslog (Datagram) > > ● rsyslog.service - System Logging Service > Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled) > Active: inactive (dead) > Docs: man:rsyslogd(8) > http://www.rsyslog.com/doc/ > > # systemctl is-enabled rsyslog.service > enabled
Well, something or someone stopped the rsyslog service on Sep 4 22:38:09. So it's obvious you don't get anymore updates to /var/log/syslog. Now we need to find out, why rsyslog.service (and syslog.socket) was stopped. Can you please reboot, add "systemd.log_level=debug" to the kernel command line, and then attach the output of "journalctl -alb" to the bug report -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
