Re: Help!!! Mysql use 99.9% of CPU!!!
Did you find any record in database "amavisd" older than days set in AMAVISD_REMOVE_MAILLOG_IN_DAYS?
----
Urgent issue? Pay iRedMail developer to solve it remotely at $29.Works on Red Hat Enterprise Linux, CentOS, Scientific Linux, Debian, Ubuntu, openSUSE, Gentoo, FreeBSD, OpenBSD
You are not logged in. Please login or register.
Did you find any record in database "amavisd" older than days set in AMAVISD_REMOVE_MAILLOG_IN_DAYS?
----
Urgent issue? Pay iRedMail developer to solve it remotely at $29.Did you find any record in database "amavisd" older than days set in AMAVISD_REMOVE_MAILLOG_IN_DAYS?
I'm sorry for the lag but I see your reply just now...
I'm not sure I understand what you mean and how to do it...
I'm not sure I understand what you mean and how to do it...
For example, if you set 'AMAVISD_REMOVE_MAILLOG_IN_DAYS = 7' to keep old records for 7 days, is there any records older than 7 days after you execute the script to clean up database records?
posa68 wrote:I'm not sure I understand what you mean and how to do it...
For example, if you set 'AMAVISD_REMOVE_MAILLOG_IN_DAYS = 7' to keep old records for 7 days, is there any records older than 7 days after you execute the script to clean up database records?
I think the script does'n clear the db, I have too many records inside amavisd:
maddr -> 79340 rows -> 14.1 MB
msgcrpt -> 90567 rows -> 20 MB
msgs -> 268087 rows -> 128.3 MB
How can I safely delete all unnecessary records?
Thanks...
There are two time related columns in `amavisd.msgs`: time_num, time_iso, you can delete old records based on them.
Note: `msgrcpt.mail_id` = `msgs.mail_id`.
There are two time related columns in `amavisd.msgs`: time_num, time_iso, you can delete old records based on them.
Note: `msgrcpt.mail_id` = `msgs.mail_id`.
And if I wish to remove ALL this records?
Can I use statement "truncate tablename" ?
Thanks.
Can I use statement "truncate tablename" ?
Yes you can.
When running the script I get
Lock wait timeout exceeded; in the logs, any idea how to fix this
When running the script I get
Lock wait timeout exceeded; in the logs, any idea how to fix this
Looked like i have about 1.4 gig of logs so I truncate the tables manually seems like it works now.
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
Generated in 0.051 seconds (89% PHP - 11% DB) with 9 queries