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

[Michael Biebl]

Am 25.02.2015 um 22:18 schrieb Christian Seiler:
> Control: tags -1 - moreinfo
> 
> Am 2015-02-25 21:27, schrieb Michael Biebl:
>> Am 25.02.2015 um 18:59 schrieb Christian Seiler:
>>> Control: severity -1 serious
>>>
>>> Thoughts?
>>
>> Those missing syslog messages (only) happen when systemd flushes the
>> initial boot kernel/messages to the syslog socket, right?
> 
> Not exactly, journald flushing is only for journald's own storage.

Well, yeah, that's not what I meant.
My point was the early boot messages which accumulate and get dumped to
the syslog socket in a short period of time (with possibly no reader up
yet).

>> Once the syslog daemon is running, do you still get messages about
>> syslog messages being dropped?
> 
> The original reporter of the bug noticed this during normal
> operations. Also, just trying some trivial things, I could
> reproduce it with for example:
> 
> for i in $(seq 1 1000); do systemd-cat ls -l /usr/bin & done
> 
> Warning: this will produce millions of log messages and take a while.
> (I overdid that, you can probably just do seq 1 10 or something.
> journald will rotate this quite a few times during operation...)

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.

-- 
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/20150225/99bfa7c3/attachment-0002.sig>