How can I fix empty mail log information in Warden?

Warden uses the systemd-journal to lookup mail log information. If your logs are empty you might have a corrupted journal.

Check the Journal For Errors

journalctl --verify

Pruning the systemd-journal Examples 

Usually pruning the journal will fix the corrupted data. Here are come different examples:

// Remove all files older than 7 days
journalctl --vacuum-time=7d 

// limit the journal to 1 GB
journalctl --vacuum-size=1G 

// Reset the entire journal if it is broken
journalctl --vacuum-time=0d 

// for more help about all the options
man journalctl

Enable Persistent Logging

You can view how to enable persistent logging and expand journal retention times here.

  • journalctl, logging, empty, systemd-journal, retention
  • 4 Users Found This Useful
Was this answer helpful?

Related Articles

How can I fix the error: "milter-reject: END-OF-MESSAGE from..." in the log and found the AV in error (cannot read /etc/clam.d/scan.conf).

Cloudlinux / Imunify360 added their own version of ClamAV to their repo which accidentally...

How can I fix the error: Can't connect to TCP port 10024 on ::1 [Cannot assign requested address] when trying to start Amavis?

When trying to start Amavis you see this in the mail log: Oct 02 03:20:15 condor3648 systemd[1]:...

How can I fix the error: Error [Contentfilter_Settings_Contentfilter]. Message [[QUARANTINEDIR] must be a valid directory?

This error means that Amavis was not installed correctly. Try running the Warden from the command...

How can I fix the error: host 127.0.0.1[127.0.0.1] said: 552 5.3.4 Declared message size (1208029 B) exceeds size limit for recipient?

You can set the message size limit for Amavis under Settings -> Policy Settings -> Misc...

How can I fix the error: milter-reject: DATA 451 4.7.1 Service unavailable - try again later?

Reject log In the Warden reject log you see the message: Service unavailable - try again later....