I’m using Mysql (version : 5.0.24) which is accessed by web application developed by ASP.NET 2.0 .The version of the .net connector i’m using is 5.0.7.0 .Now the problem is the DB service is crashing unexpectedly i.e. the DB service is stopped & to be started manually. This to happening in irregular intervals. Some times it’s happening for every 3 days & in sometimes its happening for every 7 days.
The log entry in the error log is given below.
090126 3:05:00 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...
090126 3:05:00 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 3 3969103191.
InnoDB: Doing recovery: scanned up to log sequence number 3 3969103932
090126 3:05:00 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
090126 3:05:01 InnoDB: Started; log sequence number 3 3969103932
090126 3:05:01 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.24-community-nt-log' socket: '' port: 3306 MySQL Community Edition (GPL)
In one of the mysql forums somebody posted that if the log files has “-” in its name, that may lead to crash. I’ve ensued that log files doest have “-” in its name. Still the problem exists. What might be the possible reasons for crashing DB like this?