mailwatch error

[Tony Enderby]

The table may have reached its size limit ..

Try the following suggestion from the mailwatch list archives.

--------------------
Connect to the mysql daemon using the mysql command-line tool as a user
with
rights to your mailscanner database, switch to the mailscanner database
if
needed ("use mailscanner"), and run the following sql code:

delete low_priority quick from maillog
where timestamp < (now() - interval 14 day);
optimize table maillog;

However, YMMV and if it breaks something, you keep both pieces.  This
fails
if you don"t have plenty of free space on the filesystem holding the
database (typically found under /var/lib/mysql), and I can"t offer you
any
good guidelines on figuring out what constitutes "plenty of free space".
 If
it blows up on me, I just nuke the database and create an empty one. :-)




Dhawal Doshy <dhawal at NETMAGICSOLUTIONS.COM>
Sent by: MailScanner mailing list <MAILSCANNER at JISCMAIL.AC.UK>

05/24/2005 08:28 PM
                               Please respond to
             MailScanner mailing list <MAILSCANNER at JISCMAIL.AC.UK>


To
MAILSCANNER at JISCMAIL.AC.UK
cc
Subject
Re: mailwatch error




Martin Hepworth wrote:
> Greg
>
> Looks like the table is fubar-ed.
>
> Have you tried a myisamchk on the table?
>
> There's some stuff in the mysql help pages about this.
>
> It could also be related to the 2GB file size - maybe you
> mysql/file-system can't handle more than 2GB per file??? Do you managed
> the amount of data in the maillog file (ie move or delete it to keep
> only the last few weeks data in the table)?
>
> Greg Matthews wrote:
>
>> slightly off-topic I know, I'm getting an error in mailwatch:
>>
>> Error executing query:
>>
>> Can't open file: 'maillog.MYD'. (errno: 144)
>>
>> I've located the file and it is almost 2GB in size. It is bigger on my
>> other relays so presumably it is not the size causing the problem. Is
my
>> DB stuffed? Is there a way to correct it or should I start again with
an
>> empty DB? if so how?
>>

I posted this to the mailwatch list sometime back, my maillog_archive
table (where i archive my maillog table) stopped growing beyond 4GB.
This behavior was explained here:
http://dev.mysql.com/doc/mysql/en/full-table.html

For large database support you'll need to do the following:
a. Specify MAX_ROWS=value during table creation.
OR
b. ALTER TABLE maillog MAX_ROWS=1000000000(replace with required value);

one more reference:
http://dev.mysql.com/doc/mysql/en/create-table.html

Also like Martin mentioned, an myisamchk -r (-o) ought to be the first
thing to try.

- dhawal

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the Wiki (http://wiki.mailscanner.info/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the Wiki (http://wiki.mailscanner.info/)
and the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!