ittermittent problem on mysql1.fluidhosting.com

[FH-Dave]

We are currently having an ittermittent MYSQL problems on mysql1.fluidhosting.com (which is also mysql2.fluidhosting.com). We are getting high server/CPU usage. We will try to fix this problem as soon as possible. Your connection to mysql server might be ittermittent.

[FH-Dave]

We will be recompiling the kernel soon to support higher open files limit and mem limit, which seems to be necessary for MySQL 4.0.x running on FreeBSD.

[FH-Dave]

Kernel has been recompiled. We have also found out that adding 66.150.201.92 (old mysql1.fluidhosting.com IP address) IP to the mysql server had caused mysql server to consumed heavy CPU resources, though for no reason yet known.

Currently mysql server seems to be performing well with the new kernel compile and without the IP 66.150.201.92 assigned. We will keep monitoring the mysql server.

[FH-Dave]

we will be doing some test that may affect mysql server.

[FH-Dave]

MYSQL server has been upgraded to 4.0.18. MySQL has been compiled with linux-thread support.

[FH-Dave]

MySQL server has been running for more than one hour without any problem. Looks like we may have solved the problem. The problem seemed to be a bug with MySQL 4.0.17. Even a small SQL query (insert table) may cause the MySQL server to hang and became unresponsive.

We have upgraded MySQL to 4.0.18 with Linux-thread support. So fare, everything looks good.

Some tables may got corrupted because when MySQL server crashed. Please contact us at support [at] fluidhosting.com if you have a problem with your database. Usually, this table corruption can be easily fixed.

April has not been a good month for us so far. Please accept our apology again for the problem. We will count this towards our SLA.