Re: journal stopping after sending logs on reboot

[Brad Zynda <bradley.v.zynda@xxxxxxxx>]

Hi Lennart,

So it looks like Jounald.conf Storage=none does not work as it says:

"none" turns off all storage, all log data received will be dropped.
Forwarding to other targets, such as the console, the kernel log buffer,
or a syslog socket will still work however. <- does not forward to
syslog socket

Changed it back to auto and it is logging but is now creating local logs
through journal stdout again :/

Thanks,
Brad

On 12/21/18 12:05 PM, Lennart Poettering wrote:
> On Fr, 21.12.18 11:57, Brad Zynda (bradley.v.zynda@xxxxxxxx) wrote:
> 
>> Hi Lennart,
>>
>> Its systemd.x86_64 219-62.el7         @centos7-x86_64
>>
>> CentOS 7.6   3.10.0-957.1.3.el7.x86_64
> 
> So yeah, my educated guess is that rsyslog is configured for you to
> pick the data from journald for the mentioned reasons, and not
> expecting the data through forwarding. if you really want to use
> forwarding, figure out how to turn that on in rsyslog.
> 
> Lennart
> 
> --
> Lennart Poettering, Red Hat
> 
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel