I'm using Amazon AWS as my host (running on an instance type c1.medium dedicated for my ARP mail server).
In my crontab file ("sudo crontab -e" on Ubuntu) I have this command to run the script every 5 minutes:
*/5 * * * * /root/clearArpLogs.sh>/dev/null 2>&1
And the contents of clearArpLogs.sh are:
You will need to replace DBUSER, DBPASS, and DBNAME with the proper values for your database information. Also the LIMIT 50000 can be reduced once the logs table has been deleted to a reasonable size.
Since I'm using InnoDB for my database engine, the actual database files won't shrink in size on disk unless I run an ALTER TABLE command, and I haven't decided when/if I'm going to do that or not yet.
I ran into same problem. Just logged into PHP Myadmin and truncated all the table for that table. Freed up 26 GB of data. ARPReach wasn't affected at all.
Josiah Poirier
After using arpReach for about a year, the database has grown to over 25GB. It looks like most of the storage is in the arpr_logs table. It seems like this is just storing subject and some basic info about emails that were sent. Is there a way that we could get that table added to the auto-purge jobs to help keep the database at a more reasonable size?
Thanks!
4 people like this idea