I dont know exactly which log-file You talk about. But I found one .err file in the MySQL Server 5.0\Data folder. Here is some data from it:
--- start ---
090427 1:14:03 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...
InnoDB: Page directory corruption: supremum not pointed to
090427 1:14:03 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 00000000000000000000000000
090427 1:14:04 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 directory corruption: supremum not pointed to
090427 1:14:04 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 00000000000000000000000000
090427 1:14:04 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
090427 1:14:04 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=0
read_buffer_size=65536
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_conn
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=00000000
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
006CF686 mysqld-nt.exe!page_cur_sea
006774A7 mysqld-nt.exe!btr_cur_sear
006AFB3E mysqld-nt.exe!btr_pcur_ope
006A2355 mysqld-nt.exe!dict_load_in
006A3164 mysqld-nt.exe!dict_load_sy
006B87E0 mysqld-nt.exe!dict_boot()[
006657A9 mysqld-nt.exe!innobase_sta
004447A2 mysqld-nt.exe!innobase_ini
0044B23D mysqld-nt.exe!ha_init()[ha
004B801E mysqld-nt.exe!init_server_
004BBE45 mysqld-nt.exe!win_main()[m
004BC20B mysqld-nt.exe!mysql_servic
006DF00F mysqld-nt.exe!_threadstart
77E6482F kernel32.dll!GetModuleHand
The manual page at http://dev.mysql.com/doc/m
information that should help you find out what is causing the crash.
InnoDB: Error: log file .\ib_logfile0 is of different size 0 10485760 bytes
InnoDB: than specified in the .cnf file 0 52428800 bytes!
090427 1:15:36 [ERROR] Default storage engine (InnoDB) is not available
090427 1:15:36 [ERROR] Aborting
090427 1:15:36 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete
InnoDB: Error: log file .\ib_logfile0 is of different size 0 10485760 bytes
InnoDB: than specified in the .cnf file 0 52428800 bytes!
090427 1:23:10 [ERROR] Default storage engine (InnoDB) is not available
090427 1:23:10 [ERROR] Aborting
090427 1:23:10 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete
InnoDB: Error: log file .\ib_logfile0 is of different size 0 10485760 bytes
InnoDB: than specified in the .cnf file 0 52428800 bytes!
090427 15:29:41 [ERROR] Default storage engine (InnoDB) is not available
090427 15:29:41 [ERROR] Aborting
090427 15:29:41 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete
--- end ---
Could You use that for something?
PS: All my tables are MyISAM except 1 that is InnoDB.
When I install MySQL server, I of course therefore dont choose InnoDB as my primary db engine.
Main Topics
Browse All Topics





by: theGhost_k8Posted on 2009-04-26 at 20:56:38ID: 24238797
Go to your data directory where you will find the error log, check out for actual error there!!