If you’re seeing a message like “Exim paniclog has non-zero size, mail system might be broken” in your Exim log file, don’t worry – you’re not the only one. This is a common error that can occur for a variety of reasons, and fortunately, it’s usually easy to fix. In this post, we’ll walk you through how to troubleshoot and fix the Exim paniclog issue. Stay calm – your email is probably still working just fine!

Error Code

exim paniclog /var/log/exim4/paniclog on [DomainName.com] has non-zero size, mail system might be broken. The last 10 lines are quoted below.


If your exim is up and running, there’s no need to worry. You can easily check the log files to see what the problem was. Exim automatically records all activity in log files, so simply looking through these files will give you a clear picture of what went wrong. In most cases, exim will automatically restart itself after an error, so you shouldn’t need to do anything manually. If your exim does go down for some reason, simply restart it to get it up and running again.

cat /var/log/exim4/paniclog

The paniclog is a log file that is created when the server detects an error. This log file can be useful for debugging purposes, but it can also take up a lot of disk space. If you no longer need the paniclog, then you can erase it with the following command:

truncate -s 0 /var/log/exim4/paniclog

This will clear the log errors file from the log file and stop the email warnings.