MYSQL databases keeps CRASHING on my new server!
 

I've been moving all my sites to my new server. I noticed that some of them were losing traffic, and the MYSQL database was corrupted for my trading script. I thought it was a problem with that script and changed to a different script... after a day or so, THAT MYSQL DATABASE CRASHES TOO!

Has anyone else experienced these problems?


PLEASE HELP! :helpme

What OS?

Your host should be able to help you if you have a managed account.

Redhat 7.2

Post some details like OS, mysql version and anything from server.err that is helpful ;p

MYSQL - 4.0.13
PHP - 4.3.1
APACHE - 1.3.27 (Unix)

example of error:

http://ilovetitties.com/tgp/ttt-out....t=50&link=potd

Traffic Drive sites last about one or two days then I get a connection error and garbage in the HURL table...

TTT gives me the error I posted above... this site was working for about a day or two also...

GFED make sure your not taking a database from an i686 architure and putting it on i386 or vice versa

if so dump the database and reimport it

Also check that the my.cnf files on both servers are setup the same.

My :2 cents:

The databases have been created in Cpanel and all entries were reentered by hand... what directory is my.cnf in?


Thanks

usually it is /etc/my.cnf or /usr/local/etc/my.cnf ... but it all depends on your setup

run this command to find it:

find / -name my.cnf

:winkwink:

my old box didn't have that file, the new one has it and contains this...

[mysqld]
set-variable = max_connections=500

You should have your admins take a look at the differences between both setups then ....

I AM the admin... :(

Hit me up on ICQ 4433144

do as he said , if he cant help you nobody can

error number 145 is when your records are corrupt.

Shutdown the DB, then run

myisamchk -ar *.MYI in your data directory

should fix the problems, if not you might need the -e or -o flags on the myisamchk (or isamchk, depending what you're using)

Then restart and everything should be cool

You don't even have to shut down the database, in the mysql client do:

However, it's a bad sign that your databases are corrupt after only that short a time. Has your server crashed during all of this?

I've learnt from experience that most times when I repair corrupted tables while it's running, it doesn't fix them..

Thanks for everyone's help! JPFdude has took a look at my boxes and determined that the # of connections was too low on my new box and kept corrupting my MYSQL databases.


Thank you all for your quick help and responses! Without GFY all my shit would have died!

So lock it first : )

How much traffic you getting through that script? Maybe someone just needs to learn how to make better indexes : )