WampServer

I've had WAMP wunning on a win 2003 web server for a little over 4 months now with no issues at all. This morning i started getting the following error:

Can't connect to MySQL server on 'localhost' (10061)

Did some research, and most people point to the SQL server not running. After some time trying to fix the current install of wamp i eventually gave up and decided to reinstall it.

Now that its all reinstalled i start the server and MYSQL runs, but for only about 15 seconds and then dies and starts returning the above errors again.


Any suggestions?

open c:./wamp/bin/mysql/mysql5.051b/logs and paste up the mysql log here

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]

Never mind. Entirely my wrong doing. ( I am crying inside about the lost database though.)

Found the issue. Turns out the database was corupt/not copied properly from a file transfer.


My theory is, Any sort of access the the data base was causeing the problem and crashing MySQL.


There doesnt appear to be any 'logs' folder in the above mentioned directory. but there is at C:\wamp\logs

in the mysql.log file, the bellow is one of the many repeat error logs.


080531 22:25:01 InnoDB: Started; log sequence number 0 45619
080531 22:25:01 [Note] wampmysqld: ready for connections.
Version: '5.0.45-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
080531 22:25:09 [ERROR] Table .\my_tip\nrl_fixtures has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.
080531 22:25:09 [Warning] Table .\my_tip\nrl_fixtures key_used_on_scan is 0 even though there is no primary key inside InnoDB.
080531 22:25:09080531 22:25:09 [ERROR] Table my_tip/nrl_fixtures contains fewer indexes inside InnoDB than are defined in the MySQL .frm file. Have you mixed up .frm files from different installations? See [dev.mysql.com]

080531 22:25:09 [ERROR] Innodb could not find key n 0 with name PRIMARY from dict cache for table my_tip/nrl_fixtures
080531 22:25:09 [ERROR] Table .\my_tip\nrl_fixtures has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.
080531 22:25:09 [Warning] Table .\my_tip\nrl_fixtures key_used_on_scan is 0 even though there is no primary key inside InnoDB.
080531 22:25:09080531 22:25:09 [ERROR] Table my_tip/nrl_fixtures contains fewer indexes inside InnoDB than are defined in the MySQL .frm file. Have you mixed up .frm files from different installations? See [dev.mysql.com]



Edited 1 time(s). Last edit at 05/31/2008 03:16PM by ian_b.

as u can see you have curropted the database,...
u=it cant find the indexes in the table,..

start again , im afraid,

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]