Error: MySQL shutdown unexpectedly.

[lmt12345]

Hi,

Please help with why this is shutting down unexpectedly.

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

Apologies if it is a silly error I jut need it fixed ASAP as I have work due that uses XAMPP on Friday

[Altrea]

Hi,

your logs don't contain any helpful information about your issue.

Please try to start MariaDB as console application and tell us what log messages you get there:

• start the XAMPP shell by clicking the [Shell] button in your XAMPP control panel
• execute the following command
  

  Code: Select all

  mysqld --defaults-file=mysql\bin\my.ini --standalone --console

[lmt12345]

Thank you so much for your reply. I have done this but the error log is too long to post here. are there any key things I should look for in my error log or websites I can use to help me find what in the error log is the problem?

[Altrea]

The error log in the console window is too long?
you will be the very first one with that problem.

[gulshan212]

Hello this is Gulshan Negi
Well, to resolve this error there are sevral ways such as you can check the MySQL error log to gather more information about the issue. Then, you can try troubleshooting the issue by checking for port conflicts, repairing corrupted data, increasing memory, and checking the MySQL configuration settings.
I am sure it will work.
Thanks