Bug#762700: systemd: journald fails to forward most boot messages to syslog

[Christian Seiler]

Am 2015-02-25 23:26, schrieb Michael Biebl:
> If you need that kind of throughput, using the imjournal module might
> possibly be the better choice (would need some testing, how mature
> imjournal is). Unfortunately, it's not really possible to ship a 
> default
> rsyslog configuration, which uses imjournal and works both under 
> systemd
> and alternative inits.

I just tried to think of a dead-simple way to see if I could trigger
that condition, and that was the simplest thing I could think of. I
said myself that that was an extreme example, and I really don't
need that kind of throughput.

That said, if the load is quite high for a period of time, I could
easily imagine that with a queue length of just 11, this problem
could also be triggered with a high but not extreme amount of
messages generated. And apparently that's the case, else the
original reporter of this bug wouldn't have reported it.

Also: I'm not looking for a solution that solves this for any
possible amount of log messages, but I do think that the current
limit doesn't provide enough of a safety zone that one would like
to rely on.

w.r.t. imjournal: I wouldn't really care about configuration there,
but rsyslog is built without imjournal support and syslog-ng is too
old, so syslog pulling from the journal is currently not possible
at all under Jessie, it has to be journal pushing to syslog.

And irrespective of all that, the problem of the boot messages
remains (and I don't mean only the really early ones, I mean
especially those of services ordered after $syslog under sysvinit).

Christian