Article ID: 118275, created on Oct 29, 2013, last review on Jun 17, 2016

  • Applies to:
  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux
  • Plesk 12.5 for Windows
  • Plesk 12.0 for Windows
  • Plesk 11.5 for Windows
  • Virtuozzo containers for Linux 4.7
  • Virtuozzo containers for Linux 4.6


  1. MySQL cannot start inside a container:

    ~# service mysqld start
    Timeout error occurred trying to start MySQL Daemon.
    Starting MySQL:                                            [FAILED]
  2. Upon checking MySQL logs, the following error can be observed, that indicates InnoDB corruption:

    130810 18:29:44  mysqld started
    InnoDB: Log scan progressed past the checkpoint lsn 26 2213223494
    130810 18:29:44  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: Doing recovery: scanned up to log sequence number 26 2213226852
    130810 18:29:45  InnoDB: Starting an apply batch of log records to the database...
    InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 InnoDB: Probable data corruption on page 1253469
    InnoDB: Original record (compact record)
    InnoDB: on that page.
    InnoDB: Cannot find the dir slot for record (compact record)
    InnoDB: on that page!
    130810 18:29:45  InnoDB: Page dump in ascii and hex (16384 bytes)
    130810 18:43:03  InnoDB: Page checksum 2737367751, prior-to-4.0.14-form checksum 3741771681
    InnoDB: stored checksum 2737367751, prior-to-4.0.14-form stored checksum 3741771681
    InnoDB: Page lsn 26 2211199944, low 4 bytes of lsn at page end 2211199944
    InnoDB: Page number (if stored to page already) 1253469,
    InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
    InnoDB: Page may be an index page where index id is 0 522
    130810 18:43:03InnoDB: Assertion failure in thread 1120397632 in file page0page.c line 132
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to
    InnoDB: If you get repeated assertion failures or crashes, even
    InnoDB: immediately after the mysqld startup, there may be
    InnoDB: corruption in the InnoDB tablespace. Please refer to
    InnoDB: about forcing recovery.
    130810 18:43:03 - mysqld got signal 11 ;


The InnoDB storage file of MySQL contains some kind of corruption which does not allow MySQL to use this storage further without forced recovery of the storage structure.


Process of fixing ordinary MySQL InnoDB corruption inside a container is exactly the same as in a usual hardware node. You may refer to official MySQL resources:

Forcing InnoDB Recovery.

Search Words

Event ID 100

Timeout error occurred trying to start MySQL Daemon

ERROR: Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2002] No such file or directory (Abstract.php:144)

Cannot find the dir slot for record

corruption in the InnoDB tablespace

Forcing InnoDB Recovery


Problem with Mysql after upgrade

ERROR: Zend_Db_Statement_Exception: SQLSTATE[HY000]: General error: 1030 Got error -1 from storage engine (Pdo.php:234)

e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 0c05f0c76fec3dd785e9feafce1099a9 36627b12981f68a16405a79233409a5e 742559b1631652fadd74764ae8be475e 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 e335d9adf7edffca6a8af8039031a4c7 2a5151f57629129e26ff206d171fbb5f 85a92ca67f2200d36506862eaa6ed6b8 46a8e394d6fa13134808921036a34da8 bd7fc88cf1b01f097749ae6f87272128 ed7be2b984f9c27de1d2dc349dc19c6d a766cea0c28e23e978fa78ef81918ab8 8b661cab116c79dbe6c4ac5bbdf1c8cb

Email subscription for changes to this article
Save as PDF