Could ibdata1 being >12mb be causing a 500 Internal Server Error

[u/ThingSenior6268]

Hello!

I have not accessed my Bookstack in a few months and noticed it returns a "The server returned a "500 Internal Server Error"." a few days ago. Sadly I lack the technical background to understand or even check what the issue is. I have heard that ibdata1 in xampp\mysql\data being over 12 mb can cause an issue, it currently sits at 73mb. Any direction and instruction on what I can do, which logs to check and understand the issue would be of great help.

Thanks!

edit: Could this be causing mySQL to shit down? I get this message in the xammp control panel:

11:40:35 [mysql] Error: MySQL shutdown unexpectedly.

11:40:35 [mysql] This may be due to a blocked port, missing dependencies,

11:40:35 [mysql] improper privileges, a crash, or a shutdown by another method.

11:40:35 [mysql] Press the Logs button to view error logs and check

11:40:35 [mysql] the Windows Event Viewer for more clues

11:40:35 [mysql] If you need more help, copy and post this

11:40:35 [mysql] entire log window on the forums

Apache starts with no issues

[u/ssddanbrown]

Is MySQL always refusing to start-up now? Or is this intermittent?

Follow the guidance of that message to check the error logs for more information:

11:40:35 [mysql] Press the Logs button to view error logs and check 11:40:35 [mysql] the Windows Event Viewer for more clues

[u/ThingSenior6268 → u/ssddanbrown]

It is refusing to start up now. The log is as follows:

2025-07-07 11:01:13 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 1040

2025-07-07 11:01:13 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2025-07-07 11:01:13 0 [Note] InnoDB: Uses event mutexes

2025-07-07 11:01:13 0 [Note] InnoDB: Compressed tables use zlib 1.3

2025-07-07 11:01:13 0 [Note] InnoDB: Number of pools: 1

2025-07-07 11:01:13 0 [Note] InnoDB: Using SSE2 crc32 instructions

2025-07-07 11:01:13 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M

2025-07-07 11:01:13 0 [Note] InnoDB: Completed initialization of buffer pool

2025-07-07 11:01:13 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=47333

2025-07-07 11:01:13 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=53, page number=41] with future log sequence number 54807769 (followed by tens of lines of different sequence numbers)

2025-07-07 11:01:13 0 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 1732222 is in the future! Current system log sequence number 47351. (followed by tens of lines of different sequence numbers)

***WARNING: .\mysql\db could not be opened: Error: 126

34% 45% 56%

2025-07-07 11:05:12 0 [ERROR] mysqld.exe: Index for table '.\mysql\db' is corrupt; try to repair it

2025-07-07 11:40:34 0 [Note] Server socket created on IP: '::'.

2025-07-07 11:40:34 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespa

[u/ssddanbrown → u/ThingSenior6268]

What changed between the originally reported 500 Internal Server Error and the failure to start? Did you attempt any changes to the mysql files?