Support » Localhost Installs » easyphp_ error mysql

  • Resolved casti_87

    (@casti_87)


    Hi,
    I downloaded WP to work locally, I also installed EasyPHP and everything was working perfectly , WP is installed and I have started to work. Today I restart the pc easyphp gives me an error on starting mySQL , and the log shows this :

    5124 01/09/2014 23:05:54 [Note] Plugin ‘ FEDERATED ‘ is disabled .
    6d8 01/09/2014 23:05:54 InnoDB : Warning: Using innodb_additional_mem_pool_size is DEPRECATED . This option may be removed in future releases , together with the option innodb_use_sys_malloc and with the InnoDB ‘s internal memory allocator .
    5124 01/09/2014 23:05:54 [Note] InnoDB : The InnoDB memory heap is disabled
    5124 01/09/2014 23:05:54 [Note] InnoDB : Mutexes and rw_locks use Windows interlocked functions
    5124 01/09/2014 23:05:54 [Note] InnoDB : Compressed tables use zlib 1.2.3
    5124 01/09/2014 23:05:54 [Note] InnoDB : Not using CPU instructions crc32
    5124 01/09/2014 23:05:54 [Note] InnoDB : Initializing buffer pool , size = 16.0m
    5124 01/09/2014 23:05:54 [Note] InnoDB : Completed initialization of buffer pool
    5124 01/09/2014 23:05:54 [Note] InnoDB : Highest supported file format is Barracuda .
    5124 01/09/2014 23:05:54 [Note] InnoDB : The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2917617 in the ib_logfiles !
    5124 01/09/2014 23:05:54 [Note] InnoDB : Database was not shut down normally !
    5124 01/09/2014 23:05:54 [Note] InnoDB : Starting crash recovery .
    5124 01/09/2014 23:05:54 [Note] InnoDB : Reading tablespace information from the . Ibd files …
    09.01.2014 23:05:54 5124 [ ERROR] InnoDB : Attempted to open a previously opened table space. Previous tablespace database_eterotopie / wp_term_taxonomy uses space ID: 4 filepath at : . \ Database_eterotopie \ wp_term_taxonomy.ibd . Can not open tablespace mysql / slave_master_info Which uses space ID: 4 filepath at : . \ Mysql \ slave_master_info.ibd
    InnoDB : Error : could not open single-table tablespace files . \ Mysql \ slave_master_info.ibd
    InnoDB : We do not continue the crash recovery , Because The table may become
    InnoDB : corrupt if we can not apply the log records in the InnoDB logs to it .
    InnoDB : To fix the problem and start mysqld :
    InnoDB : 1 ) If there is a permission problem in the mysqld file and can not
    InnoDB : open the file , You Should modify the permissions.
    InnoDB : 2 ) If the table is not needed , or you can restore it from a backup ,
    InnoDB : then you can remove the . Ibd file , and InnoDB will do a normal
    InnoDB : Crash recovery and ignore That table .
    InnoDB : 3 ) If the file system or the disk is broken , and you can not remove
    InnoDB : the . Ibd file , you can innodb_force_recovery September > 0 in my.cnf
    InnoDB : and force InnoDB crash recovery to continue here .

    I searched the internet and the problem recurs, I followed all the directions :
    restart the pc
    restarted easyphp
    verified that Skype is closed
    check all permissions
    easyphp started as administrator
    I also followed the instructions in the log by deleting the file . ibd

    I do not know how to solve the problem , if I uninstall honestly do not know how not to lose the data entered in wordpress.

    please help me

Viewing 5 replies - 1 through 5 (of 5 total)
  • Do you have database backup of your WP install?

    Thread Starter casti_87

    (@casti_87)

    yes

    Then what about installing a new copy of EasyPHP in a different location, porting your old folders over, re-installing WordPress and finally importing your db backup? You have nothing to lose except about 1 hour’s work or less and your current issues do sound like there’s permanent damage to the old EasyPHP install.

    Thread Starter casti_87

    (@casti_87)

    I try, thank you so much!!

    Thread Starter casti_87

    (@casti_87)

    Finally I I deleted easyphp because everytime I turn off the pc it has a problem. After I installed XAMPP it is perfect.
    problem solved.

    thanks

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘easyphp_ error mysql’ is closed to new replies.