Jump to content
php.lv forumi

MySQL server problēma


php newbie

Recommended Posts

uzkaras skripts un MySQL serveri nevar piestartēt:
 

130224 13:11:28 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
InnoDB: Compressed tables use zlib 1.2.3
130224 13:11:28  InnoDB: Initializing buffer pool, size = 16.0M
130224 13:11:28  InnoDB: Completed initialization of buffer pool
130224 13:11:28  InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130224 13:11:28  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: Database page corruption on disk or a failed
InnoDB: file read of page 245.
InnoDB: You may have to recover from a backup.
InnoDB: End of page dump
130224 13:11:30  InnoDB: Page checksum 2870860906, prior-to-4.0.14-form checksum 372330996
InnoDB: stored checksum 1529325762, prior-to-4.0.14-form stored checksum 372330996
InnoDB: Page lsn 0 682665087, low 4 bytes of lsn at page end 682665087
InnoDB: Page number (if stored to page already) 245,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a system page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 245.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.



sanāca piestartēt ar innodb_force_recovery = 5, kas nozīmē: Do not look at undo logs when starting the database: InnoDB treats even incomplete transactions as committed.

Un kā izlabot?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...