Receiving an Error trying to connect to mySQL

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

Receiving an Error trying to connect to mySQL

Postby KnoxVegas » 14. January 2019 16:08


I have setup my xampp to work with syncing to my dropbox account, I can in over the weekend back to work to find out that the mySQL is not wanting to connect, saying its a bad port possibly? But I know the ports are not being block? Here is the error log I'm getting. I could be wrong, but not sure what is going on here?

Code: Select all
2019-01-14 10:08:07 2830 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.
2019-01-14 10:08:07 10288 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-01-14 10:08:07 10288 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-14 10:08:07 10288 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-14 10:08:07 10288 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-01-14 10:08:07 10288 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-01-14 10:08:07 10288 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-01-14 10:08:07 10288 [Note] InnoDB: Using generic crc32 instructions
2019-01-14 10:08:07 10288 [Note] InnoDB: Initializing buffer pool, size = 30.0M
2019-01-14 10:08:07 10288 [Note] InnoDB: Completed initialization of buffer pool
2019-01-14 10:08:07 10288 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-14 10:08:07 10288 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence number 575443617 in the ib_logfiles!
2019-01-14 10:08:07 10288 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace joinssncurrent/wp_options (68LSQ22's conflicted copy 2019-01-14) uses space ID: 547 at filepath: .\joinssncurrent\wp_options (68lsq22's conflicted copy 2019-01-14).ibd. Cannot open tablespace joinssncurrent/wp_options which uses space ID: 547 at filepath: .\joinssncurrent\wp_options.ibd
InnoDB: Error: could not open single-table tablespace file .\joinssncurrent\wp_options.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.
190114 10:08:07 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.1.29-MariaDB
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787116 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
The manual page at contains
information that should help you find out what is causing the crash.
Posts: 1
Joined: 14. January 2019 16:05
XAMPP version: 3.2.2
Operating System: Windows 10

Re: Receiving an Error trying to connect to mySQL

Postby Altrea » 14. January 2019 18:58

yet another Dropbox corrupted MariaDB instance...
Waiting for the time people realizing that Dropbox is not suitable for syncing Databases.
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: 9683
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: No registered users and 61 guests