[SOLVED] MySQL server won't start anymore.

[scriptdaemon]

I've had it installed for a few weeks, and only until today did I notice it just didn't want to work anymore. I first noticed by opening phpMyAdmin, which gave me this error:

 

#2003 - The server is not responding

 

Then, I tried my own scripts, which gave me:

 

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

 

I've come to the most likely conclusion that somehow the innodb tables got corrupted, as my error log gives me:

 

071109 15:43:14  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
071109 15:43:14  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 613833.
InnoDB: Doing recovery: scanned up to log sequence number 0 613833
InnoDB: Page directory corruption: infimum not pointed to
071109 15:43:14  InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex *Insert a whole lot of 0s here* ; asc *Insert a whole lot of spaces here* ;InnoDB: End of page dump
071109 15:43:14  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
InnoDB: Page directory corruption: supremum not pointed to
071109 15:43:14  InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex *Insert a whole lot of 0s here* ; asc *Insert a whole lot of spaces here* ;InnoDB: End of page dump
071109 15:43:14  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
071109 15:43:14InnoDB: Error: trying to access a stray pointer 81F03FF8
InnoDB: buf pool start is at 01EF4000, end at 026F4000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: how to force recovery.
071109 15:43:14  InnoDB: Assertion failure in thread 3916 in file f:\build\mysql-6.0.2-alpha-winbuild\mysql-community-nt-6.0.2-alpha-build\storage\innobase\include\buf0buf.ic line 264
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
071109 15:43:14 [ERROR] mysqld: Got signal 11. Aborting!

071109 15:43:14 [ERROR] Aborting

071109 15:43:14 [Note] mysqld: Shutdown complete

 

(Large number of 0s and spaces truncated, noted inside the log)

 

I've tried reconfiguring MySQL, reinstalling, forcing recovery as mentioned in the link given to me in the error log, etc. and still no avail. Even when I use the MySQL Command Line Client, as soon as I enter my password, it closes. When I first installed I already opened the port to allow MySQL to run, and even now I added it to Windows Firewall just in case, also to no avail.

 

EDIT: Another note: I'm not sure why, but "f:\build\mysql-6.0.2-alpha-winbuild\mysql-community-nt-6.0.2-alpha-build\storage\innobase\include\buf0buf.ic" seems odd, as I don't have an f:\. Could this be the problem, or is that supposed to happen?

[hitman6003]

I'm guessing since you're using alpha software (MySQL 6.0.2), that could be a major cause of your problems.  Have you checked their bug reports?

 

I haven't played with MySQL 6 yet, but I would imagine that it's much the same as MySQL 5 in that if the InnoDB table spaces do not exist, then it will attempt to create them upon first run.

 

Check your my.cnf / my.inf and make sure that the location for your data files is defined, delete any current table space files (for innodb) and restart the daemon / service.

[scriptdaemon]

I did a complete uninstall and switched to 5.0 and it works. I guess I'll just wait for 6.0 later.