kangle mysql打不开_kangle mysql挂了 求救

2018-09-0210:53:351900[Note]InnoDB:UsingCPUcrc32instructions2018-09-0210:53:351900[Note]InnoDB:Initializingbufferpool,size=8.0M2018-09-0210:53:351900[Note]InnoDB:Complete...

2018-09-02 10:53:35 1900 [Note] InnoDB: Using CPU crc32 instructions

2018-09-02 10:53:35 1900 [Note] InnoDB: Initializing buffer pool, size = 8.0M

2018-09-02 10:53:35 1900 [Note] InnoDB: Completed initialization of buffer pool

2018-09-02 10:53:35 1900 [Note] InnoDB: Highest supported file format is Barracuda.

2018-09-02 10:53:35 1900 [Note] InnoDB: The log sequence numbers 1600627 and 1600627 in ibdata files do not match the log sequence number 2304315 in the ib_logfiles!

2018-09-02 10:53:35 1900 [Note] InnoDB: Database was not shutdown normally!

2018-09-02 10:53:35 1900 [Note] InnoDB: Starting crash recovery.

2018-09-02 10:53:35 1900 [Note] InnoDB: Reading tablespace information from the .ibd files...

2018-09-02 10:53:35 1900 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace kangle/flow_day uses space ID: 4 at filepath: ./kangle/flow_day.ibd. Cannot open tablespace mysql/slave_master_info which uses space ID: 4 at filepath: ./mysql/slave_master_info.ibd

2018-09-02 10:53:35 7f0a17779720 InnoDB: Operating system error number 2 in a file operation.

InnoDB: The error means the system cannot find the path specified.

InnoDB: If you are installing InnoDB, remember that you must create

InnoDB: directories yourself, InnoDB does not create them.

InnoDB: Error: could not open single-table tablespace file ./mysql/slave_master_info.ibd

InnoDB: We do not continue the crash recovery, because the table may become

InnoDB: corrupt if we cannot apply the l

展开