Apache Friends Support Forum

Yes thats right I am getting the same error that many others are getting. This happened to me about three weeks ago the first time. I had been developing in XAMPP for about 3 weeks. Then one day I tried to start MySQL and I got this error. So I backed up my HTML directory and all my databases from the main sites and reinstalled XAMPP and everything has been working normal. Now after three weeks of developing I AGAIN am getting this error this morning (and have changed or installed nothing).

Here is the error log info:

Code: Select all

2023-01-23  9:16:34 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-01-23  9:16:34 0 [Note] InnoDB: Uses event mutexes
2023-01-23  9:16:34 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-01-23  9:16:34 0 [Note] InnoDB: Number of pools: 1
2023-01-23  9:16:34 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-01-23  9:16:34 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-01-23  9:16:34 0 [Note] InnoDB: Completed initialization of buffer pool
2023-01-23  9:16:34 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-01-23  9:16:34 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-01-23  9:16:34 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-01-23  9:16:34 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-01-23  9:16:34 0 [Note] InnoDB: Waiting for purge to start
2023-01-23  9:16:34 0 [Note] InnoDB: 10.4.27 started; log sequence number 189482298; transaction id 48841
2023-01-23  9:16:34 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-01-23  9:16:34 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-01-23  9:16:34 0 [Note] Server socket created on IP: '::'.

I see that quite a few people have been having this same issue recently yet the XAMPP developers have done nothing to address this issue. This is not a coincidence there must be an underlying issue with XAMPP or with my system.

Is this something with my system? How can I fix this issue without haveing to constantly reinstall and lose billable time. This is costing me money!!!

Well, you paid exactly how much for XAMPP...

The issue is not with XAMPP, but rather with MySQL/MariaDB, which XAMPP happens to bundle, but not actually develop. If it is costing you money, I suggest you find a support forum related to MySQL/MariaDB and ask there for a correction.

Froosh wrote:Well, you paid exactly how much for XAMPP...

The issue is not with XAMPP, but rather with MySQL/MariaDB, which XAMPP happens to bundle, but not actually develop. If it is costing you money, I suggest you find a support forum related to MySQL/MariaDB and ask there for a correction.

You think because something is free that "who cares if you it causes you to lose money"? What kind of a derelict response is that? I find it hard to believe that that with ALL the other people on here having the same problem that it has nothing to do with XAMPP.

So I switched to much better application strictly for Windows and its running much better than XAMPP ever has and is far more intuative. Soooo, thanks for nothing and I am done with this mess.

Not quite a "derilict" response. Like you, I am a normal user, and not employed by or supported by XAMPP. I do not rely on XAMPP for a living, but even if I did, I know enough do what I need with XAMPP, and be sure I have backups.

My view is simply based on what I observe with the application. The XAMPP Control Panel, from what I know has not changed since back in 2021, but the packages it ships with each version have changed. It may be possible that somewhere along the way something changed with the way the MySQL/MariaDB component needs stopping, but absolutely not a certainty. While it may be a common issue, that by no means indicates to me that it is XAMPP specific.

Good luck...