[SOLVED] Add another MTA to existing installation

[oldboy]

Hello,
We currently have a CentOS4 32bits with 4.5.11 running in a box with a AMD64 3000+ and 4GB RAM And about 50 Users mostly POP3 users and a few Web users. Lately we´ve experienced loooong times when sending emails (2-3 mins) specially from outlook, and sometimes outlook gives a timeout error. The network its fine also DNS. I think the specs on the server cant handle the load.

This is the what the top command shows

top - 10:42:15 up 7 days,  2:19,  1 user,  load average: 6.77, 6.72, 5.52
Tasks: 142 total,   1 running, 140 sleeping,   0 stopped,   1 zombie
Cpu(s):  6.3% us,  1.3% sy,  0.0% ni,  0.0% id, 91.4% wa,  1.0% hi,  0.0% si
Mem:   3598536k total,  3575648k used,    22888k free,    12600k buffers
Swap:  5116692k total,    35280k used,  5081412k free,  1619208k cached

So my question is, do you think that if I add another MTA server ill be able to send mails faster?

Thanks for the help

[uxbod]

First thing would be to identify why your server is running with a load > 6! When it is at its peak what is sat on the top of your process queue ? Have you modified the SpamAssassin installation at all ? Any additional RBLs ? You should also look to upgrading your ZCS installation at some point aswell. If you could update your profile as well as that is a little out of date now

[oldboy]

Originally Posted by uxbod

First thing would be to identify why your server is running with a load > 6! When it is at its peak what is sat on the top of your process queue ? Have you modified the SpamAssassin installation at all ? Any additional RBLs ? You should also look to upgrading your ZCS installation at some point aswell. If you could update your profile as well as that is a little out of date now

Yes I have modified the spamAssasin install to block spoofers, but the server was already over 6 when i did that.
I dont want to upgrade until I dont solve this, I also been thinking to change to a more powerful box with Ubuntu.
Profile updated :P
This the TOP output

top - 09:50:41 up 10 days,  1:28,  2 users,  load average: 6.76, 5.22, 4.44
Tasks: 134 total,   2 running, 132 sleeping,   0 stopped,   0 zombie
Cpu(s):  8.7% us,  1.0% sy,  0.0% ni,  0.0% id, 89.0% wa,  1.3% hi,  0.0% si
Mem:   3598536k total,  3592812k used,     5724k free,     9152k buffers
Swap:  5116692k total,     5104k used,  5111588k free,  2409744k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
23307 zimbra    16   0  119m  26m 3640 S  9.7  0.8   7:06.63 mysqld
  337 root      15   0     0    0    0 D  0.3  0.0  14:26.59 kjournald
24031 postfix   16   0  7860 1732 1328 S  0.3  0.0   0:00.02 tlsmgr
    1 root      16   0  1796  552  472 S  0.0  0.0   0:00.85 init
    2 root      34  19     0    0    0 S  0.0  0.0   0:00.45 ksoftirqd/0
    3 root       5 -10     0    0    0 S  0.0  0.0   0:00.00 events/0
    4 root      10 -10     0    0    0 S  0.0  0.0   0:00.00 khelper
    5 root      15 -10     0    0    0 S  0.0  0.0   0:00.00 kacpid
   40 root       5 -10     0    0    0 S  0.0  0.0   0:00.00 kblockd/0
   41 root      15   0     0    0    0 S  0.0  0.0   0:00.00 khubd
   61 root       9 -10     0    0    0 S  0.0  0.0   0:00.00 aio/0
   60 root      15   0     0    0    0 S  0.0  0.0   7:17.54 kswapd0
  205 root      25   0     0    0    0 S  0.0  0.0   0:00.00 kseriod
  324 root       6 -10     0    0    0 S  0.0  0.0   0:00.00 ata/0
  326 root      22   0     0    0    0 S  0.0  0.0   0:00.00 scsi_eh_0
  327 root      23   0     0    0    0 S  0.0  0.0   0:00.00 scsi_eh_1
  330 root      19   0     0    0    0 S  0.0  0.0   0:00.00 scsi_eh_2

[oldboy]

Any recomendations anyone?
Mails sent between Zimbra users at 10:00 am are arriving at 2:00 pm. I really need your comments.

[bdial]

mysql chewing your processor usually indicates log corruption

[oldboy]

Originally Posted by bdial

mysql chewing your processor usually indicates log corruption

How do I check if I have any corruption in the logs?

[oldboy]

I have found this in /opt/zimbra/logger/db/data/my.server.com.err and it seems like its been throwing this error for a bout 3 months now, and theres thounsands of lines like this.
Could this be causing for my server to be so slow?

080810  1:10:04 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080810  1:10:04 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080810  1:10:05 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080810  1:10:05 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080810  1:10:05 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080810  1:10:05 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080810  1:10:05 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080810  1:10:05 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080811  1:10:24 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080811  1:10:24 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080811  1:10:32 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080811  1:10:32 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080811  1:10:32 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080811  1:10:32 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080811  1:10:32 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
080811  1:10:32 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed

[mmorse]

su - zimbra
logmysql zimbra_logger
check table mta;
repair table mta;

After that you might as well check the others:
show tables;
check table NAME;

[oldboy]

SOLVED... well kind of...
I had to stop the Logger service, because repairing the tables was causing my server to hang. Im waiting for a new box to upgrade to 5.x.x

[Aleks]

Hi
Just a stupid question...
In time when table was corrupted, did graphs in admin worked?

I have a same problem and I think graphs are probably the indicator for wrong hostname and/or logmysql corrupted table.
Thanks for mentioning a server hang when repairing table!

Regards, Alex