On Wed, 26 Jul 2017 11:28:43 -0400
Tom H wrote:
> I've just tried
>
> - install "rsyslog"
> - enable "rsyslog.service"
> - set "Storage=none" and "ForwardToSyslog=yes" in "/etc/systemd/journald.conf"
>
> and it worked.
It sorta worked for me. There aren't any recently updated files under
/var/log/journal, so the old binary files are no longer being
created, and I have lots and lots of /var/log/messages from booting,
but the last message in the log is:
Jul 27 09:01:24 tomh systemd-journald: Journal stopped
So it apparently decided to stop logging once the system booted :-(.
There is a /usr/lib/systemd/systemd-journald process running
and rsyslog appears to be active:
[root@tomh ~]# systemctl status rsyslog
● rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor pres
Active: active (running) since Thu 2017-07-27 09:01:28 EDT; 5min ago
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Main PID: 811 (rsyslogd)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/rsyslog.service
└─811 /usr/sbin/rsyslogd -n
I'm just no longer getting any log messages.
Anyone know how to get logging to continue after booting?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
