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

Michael Biebl biebl at debian.org
Wed Feb 25 23:04:03 GMT 2015


Am 25.02.2015 um 23:49 schrieb 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.

If we can make the journald -> syslog forwarding more robust, without
introducing side-effects, by all means, let's do that. I'm happy to take
suggestions how to achieve that.

> w.r.t. imjournal: I wouldn't really care about configuration there,
> but rsyslog is built without imjournal support

That is not true, journal support has been enabled in rsyslog for quite
a while. It's split into a separate package called "rsyslog-journal",
maybe that's why you didn't notice it?

At the time I enabled journal support in rsyslog, systemd wasn't the
default yet and I didn't want to drag in a libsystemd-journal0
dependency on basically everyones system.
Nowadays, will libsystemd0 pretty much guaranteed to installed everyone,
there is no longer a real point to split this into a separate package
and I might consider folding the modules back into the main rsyslog package.

 and syslog-ng is too
> old, so syslog pulling from the journal is currently not possible
> at all under Jessie,

True, syslog-ng-mod-journal (which afaik is an equivalent to
rsyslog-journal) is experimental only atm.

 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).

What specific problem are you talking about here?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150226/813246a7/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list