EC2 server with a crond-service and full /var/spool/exim/-folder

Solution 1:

I found the solution after hours of research.

The issue is quite simple. Crontabs are designed to place the output of the cronjob somewhere. Since this destination was not specified in my setup the destination for the output was placed in the /var/spool/exim/input-folder with one individual file per output which quickly lead to a huge amount of files and memory issues.

My solution was to specify another "destination" for the output. By adding

MAILTO=""

to the top of my crontabs, I specify the output to be sent to the email-address "". Now, the /var/spool/exim/input-folder is clean and the cronjobs are still running perfectly fine.

If you are reading this, chances are that you could use this solution as well :-)