DeepDiverMom
Programmer
For several months, we have been successfully running MySQL on a 785MB-RAM Windows NT 4.0 machine named PC4572. There are multiple GB of space available on all drives.
Today, we attempted to start an application using the following standard batch file that we have been using successfully for some time:
start D:\Release\mysql\bin\mysqld-max-nt.exe --defaults-file=D:\Release\mysql\my.cnf --standalone
We then encounter these errors in file D:\Release\mysql\data\pc4572.err:
InnoDB: ############### CORRUPT LOG RECORD FOUND
InnoDB: Log record type 14, space id 1870, page number 31276
InnoDB: Log parsing proceeded successfully up to 2 2264927680
InnoDB: Previous log record type 999999, is multi 0
InnoDB: Recv offset 0, prev 0
031202 18:05:22 D:\Release\mysql\bin\mysqld-max-nt.exe: Got signal 11. Aborting!
031202 18:05:22 Aborting
031202 18:05:22 InnoDB: Warning: shutting down a not properly started
InnoDB: or created database!
031202 18:05:22 D:\Release\mysql\bin\mysqld-max-nt.exe: Shutdown Complete
Can anyone suggest the cause and remedy for this situation?
Thanks,
Becca
Today, we attempted to start an application using the following standard batch file that we have been using successfully for some time:
start D:\Release\mysql\bin\mysqld-max-nt.exe --defaults-file=D:\Release\mysql\my.cnf --standalone
We then encounter these errors in file D:\Release\mysql\data\pc4572.err:
InnoDB: ############### CORRUPT LOG RECORD FOUND
InnoDB: Log record type 14, space id 1870, page number 31276
InnoDB: Log parsing proceeded successfully up to 2 2264927680
InnoDB: Previous log record type 999999, is multi 0
InnoDB: Recv offset 0, prev 0
031202 18:05:22 D:\Release\mysql\bin\mysqld-max-nt.exe: Got signal 11. Aborting!
031202 18:05:22 Aborting
031202 18:05:22 InnoDB: Warning: shutting down a not properly started
InnoDB: or created database!
031202 18:05:22 D:\Release\mysql\bin\mysqld-max-nt.exe: Shutdown Complete
Can anyone suggest the cause and remedy for this situation?
Thanks,
Becca