• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 671
  • Last Modified:

MySQL Stopped working

I have been running MySQL 4.1.8 on Windows 2003 for about 6 weeks and all has been very good.

I then downloaded a free trial of nod32 virus software. This worked fine with no problems,

I then purchased a full version of nod32, installed it, restaretd the server and MySQL will not start.

I get the following error message:

"Trying to start the server ...

Server could not be started."

Please help...

Should have added the folowing actions taken already:

uninstall nod32 and restart server - result: no difference

Uninstall MySQL and reinstall - result: no difference

Restarted server numerous times - result: no difference
0
brookessmith
Asked:
brookessmith
  • 3
2 Solutions
 
German_RummCommented:
Hi brookessmith,

Look in your event log (control panel/administrative toos/Event Viewer), maybe there will be more information.
Also check mysql error log. It's located in mysql\data folder.
---
German Rumm.
0
 
brookessmithAuthor Commented:
I can't get the Administrator to connect at all, but I have looked at the error log. Last entries pasted below. The record dumps were much longer but only contained Hex Zeros so I deleted the middle bits.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
050502  7:52:37  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
050502  7:52:37 [ERROR] F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Got signal 11. Aborting!

050502  7:52:37 [ERROR] Aborting

050502  7:52:37 [Note] F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Shutdown complete

050502  8:20:29  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...
050502  8:20:29  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 2947918.
InnoDB: Doing recovery: scanned up to log sequence number 0 2947918
InnoDB: Page directory corruption: supremum not pointed to
050502  8:20:29  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 0000000000000000; asc  ;InnoDB: End of page dump
050502  8:20:29  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
050502  8:20:29  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 0000000000000; asc   ;InnoDB: End of page dump
050502  8:20:29  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
050502  8:20:29 [ERROR] F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Got signal 11. Aborting!

050502  8:20:29 [ERROR] Aborting

050502  8:20:29 [Note] F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Shutdown complete

050502  8:20:46  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...
050502  8:20:46  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 2947918.
InnoDB: Doing recovery: scanned up to log sequence number 0 2947918
InnoDB: Page directory corruption: supremum not pointed to
050502  8:20:46  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 000000000; asc           ;InnoDB: End of page dump
050502  8:20:46  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
050502  8:20:46  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 0000000000; asc        ;InnoDB: End of page dump
050502  8:20:46  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
050502  8:20:46 [ERROR] F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Got signal 11. Aborting!

050502  8:20:46 [ERROR] Aborting

050502  8:20:46 [Note] F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Shutdown complete

050502 17:12:17  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...
050502 17:12:17  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 2947918.
InnoDB: Doing recovery: scanned up to log sequence number 0 2947918
InnoDB: Page directory corruption: supremum not pointed to
050502 17:12:18  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 0000000; asc           ;InnoDB: End of page dump
050502 17:12:18  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
050502 17:12:18  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 0000000000000000000000000000; asc       ;InnoDB: End of page dump
050502 17:12:18  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
050502 17:12:18 [ERROR] F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Got signal 11. Aborting!

050502 17:12:18 [ERROR] Aborting

050502 17:12:18 [Note] F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Shutdown complete

050502 17:15:52  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...
050502 17:15:52  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 2947918.
InnoDB: Doing recovery: scanned up to log sequence number 0 2947918
InnoDB: Page directory corruption: supremum not pointed to
050502 17:15:52  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 000000000000000000000; asc       ;InnoDB: End of page dump
050502 17:15:52  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
050502 17:15:52  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 0000000000000000000000000000; asc        ;InnoDB: End of page dump
050502 17:15:52  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
050502 17:15:52 [ERROR] F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Got signal 11. Aborting!

050502 17:15:52 [ERROR] Aborting

050502 17:15:52 [Note] F:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Shutdown complete

0
 
kupra1Commented:
Hi brookessmith,
let first try to start the server. Set the following:
set-variable = innodb_force_recovery = 1

in your my.cnf.

This will allow the server to run even if it finds a corrupt page.

Restart the mysql server after it.

Thanks

0
 
brookessmithAuthor Commented:
Hi sorry for massive delay. This is my live server so I needed to get it working again urgently. I'm ashamed to say that , I have temporarily ported databases to Access and this is working fine. The changes above did not allow me to start MySQL.  I now have a bit more time and would very much like to get this fixed and back onto MySQL. Peter
0
 
brookessmithAuthor Commented:
I am suspecting that the database files had become corrupted somehow. I have completely uninstalled MySQL and browser and adminsitrator and Odbc, removed the directory and reinstalled onto a different drive and all is now well.

If it is still working in 2 days time, I will close this down.
0

Featured Post

Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now