maillog stops logging?

[Walt Thiessen]

Thanks Christophe. While I'm not having that particular issue, it was a
good clue.

When I ran as person who reported the bug did: journalctl --verify

I received the following fail message:

12be230: invalid object
File corruption detected at
/run/log/journal/3357e26558b24bfdb51c6129af284914/system.journal:12be230 (of
25165824 bytes, 78%).
FAIL: /run/log/journal/3357e26558b24bfdb51c6129af284914/system.journal
(Cannot
assign requested address)

Upon visiting /run/log/journal/3357e26558b24bfdb51c6129af284914/

I didn't see a file: system.journal:12be230

Instead, I saw a bunch of files named similar to:
system\@f04b5ba11e154e67a7b5932125b0a06a-00000000001779aa-00052a28618a19b2.journal*

I'm not sure how to clear this error.

I believe I know what caused it, however. In my CustomAction.pm, I
included a logging step that reported the content of the email. I
suspect that something in the content of an email may have inserted an
illegal character or something similar. So I've removed that logging step.

Now all I need is a way to clear the journalctl error.

Walt



On 1/28/2016 8:32 AM, Christophe GRENIER wrote:
> On Thu, 28 Jan 2016, Walt Thiessen wrote:
> 
>> CentOS 7
> 
> Have you updated systemd a few days ago ?
> https://bugzilla.redhat.com/show_bug.cgi?id=1292447
>