Problem with MySQL and Wordpress

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Problem with MySQL and Wordpress

Postby php74 » 21. August 2013 09:56


I use xampp for local wordpress access. I installed xampp and create vca_wordpress database with no problem.
I install a wp directory in htdocs, and successfully start wp installation and first blog pages.
But when I logout wp, and stop xampp, it's no more possible to restart MySQL from xampp.
I receive the message below :

10:33:19 [main] Initializing Control Panel
10:33:19 [main] Windows Version: Windows 7 Home Premium 64-bit
10:33:19 [main] XAMPP Version: 1.8.3
10:33:19 [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
10:33:19 [main] Running with Administrator rights - good!
10:33:19 [main] XAMPP Installation Directory: "c:\xampp\"
10:33:19 [main] Checking for prerequisites
10:33:19 [main] All prerequisites found
10:33:19 [main] Initializing Modules
10:33:19 [Apache] XAMPP Apache is already running on port 80
10:33:19 [Apache] XAMPP Apache is already running on port 443
10:33:19 [main] Starting Check-Timer
10:33:19 [main] Control Panel Ready
10:33:28 [mysql] Attempting to start MySQL app...
10:33:29 [mysql] Status change detected: running
10:33:30 [mysql] Status change detected: stopped
10:33:31 [mysql] Error: MySQL shutdown unexpectedly.
10:33:31 [mysql] This may be due to a blocked port, missing dependencies,
10:33:31 [mysql] improper privileges, a crash, or a shutdown by another method.
10:33:31 [mysql] Press the Logs button to view error logs and check
10:33:31 [mysql] the Windows Event Viewer for more clues
10:33:31 [mysql] If you need more help, copy and post this
10:33:31 [mysql] entire log window on the forums

and the sql_log_error is the following :

2013-08-21 09:31:26 8012 [Note] Plugin 'FEDERATED' is disabled.
2013-08-21 09:31:26 1bb8 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.
2013-08-21 09:31:26 8012 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-21 09:31:26 8012 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-21 09:31:26 8012 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-21 09:31:26 8012 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-21 09:31:26 8012 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-21 09:31:26 8012 [Note] InnoDB: Completed initialization of buffer pool
2013-08-21 09:31:26 8012 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-21 09:31:26 8012 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2738716 in the ib_logfiles!
2013-08-21 09:31:26 8012 [Note] InnoDB: Database was not shutdown normally!
2013-08-21 09:31:26 8012 [Note] InnoDB: Starting crash recovery.
2013-08-21 09:31:26 8012 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-21 09:31:26 8012 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_wordpress/wp_usermeta uses space ID: 2 at filepath: .\bitnami_wordpress\wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
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 cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

It seems related to bitnami_wordpress that I tried also previously, but with the same problem when I stop xampp and restart.

When I erase C:\xampp\mysql\data\ibdata1, it's possible to restart MySQL, but no more access to localhost/vca_wordpress..

Thank you for your help
Posts: 1
Joined: 21. August 2013 09:37
Operating System: windows 7 64 bits

Re: Problem with MySQL and Wordpress

Postby Altrea » 21. August 2013 11:13

Hi php74,

If you are using XAMPP 1.8.3, it is recommend to use an earlier version of XAMPP because these versions seem to contain a MySQL bug.

bets wishes,
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
AF Moderator
Posts: 9450
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Return to XAMPP for Windows

Who is online

Users browsing this forum: mike_giambattista and 73 guests