Recently I came across an observation where we are not able to capture
normal reboot/shutdown logs on Fedora/RHEL distributions. In these
environments, systemd is responsible for starting the rsyslog service. A
service can have multiple dependencies, which influence how early or how
late rsyslog is
You could split rsyslog into two separate service instances.
Service 1 would do only one thing, read imjournal and write to file(s). This
service would not have the network.target dependency.
Service 2 would do everything else, including reading the file(s) output from
above (which survive t
Anyway, you still have the part where the system as such (kernel,
systemd) is still running and rsyslog is not running anymore. You can't
help it. You can minimize the "hole" a bit, but can't force a process to
run when it had already been shut down.
If you really have such high availability n
you could put the remote sender things in a seprate ruleset with a queue on that
ruleset, that would let the rest of the config run without the network
(accumulating early logs and gathering shutdown logs up to the point that
rsyslog gets shut down)
you can configure rsyslog to save the queue
4 matches
Mail list logo
