Hrm well unfortunately I'm not sure on how to recover what it was that
tried to log to the journal. If the issue is showing up frequently you
might be able to trace the journal daemon and find the open socket and
the process that owns it or maybe just grab enough of the message it
tried to send to figure out the sender.
On Mon, Nov 20, 2017 at 12:40 PM, Richard Thornton
I don't see any issues.
On 21 November 2017 at 05:45, Douglas, William
> I believe that's from something trying to use the journal and the
> journal was given something (that looks like maybe it could have been
> a core file based on the size) that was too large.
> See any services on the system crashing?
> On Mon, Nov 20, 2017 at 3:37 AM, Richard Thornton
> <richie.thornton(a)gmail.com> wrote:
>> I get this annoying error everytime CL boots:
>> systemd-journald: Failed to write entry (24 items, 5108370 bytes)
>> despite vacuuming, ignoring: Argument list too long
>> Any ideas, systemd journald seems to working fine?
>> I noticed today that /run/log has a bootchart svg file in it that's a very
>> similar size to the MB size of the journal entry, coincidence? Oh and with
>> 4.14 the journal entry size has jumped to 7MB.
>> Any ideas?
>> Dev mailing list