MySQL shutdown unexpectedly with weird log files

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

MySQL shutdown unexpectedly with weird log files

Postby dtommy79 » 15. February 2021 17:39

Hi,

This error keeps coming up for me (and for many of my colleagues as well) and no solution yet. The only way to fix this is a complete reinstall which is pretty ridiculous since after a couple of weeks the mysql error will come up again.

So here is what happens:

I get the usual error:

Error: MySQL shutdown unexpectedly.
This may be due to a blocked port, missing dependencies,
improper privileges, a crash, or a shutdown by another method.
Press the Logs button to view error logs and check
the Windows Event Viewer for more clues
If you need more help, copy and post this
entire log window on the forums


I also noticed a bunch of weird files in my xampp/mysql/data folder. Like these:

master-2020@002d12@002d22@002015@003a38@003a49@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@000d.info
master-version@003a@0020@002710@002e4@002e17@002dmariadb@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d.info
mysql-relay-bin-2020@002d12@002d22@002015@003a38@003a49@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@000d.000001
relay-log-2020@002d12@002d22@002015@003a38@003a49@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@000d.info

I tried to remove them, I also tried to remove the ib_logfile0 and the ibdata1 file.

This is what I have in the mysql_error log

2021-02-15 17:20:41 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2021-02-15 17:20:41 0 [Note] InnoDB: Uses event mutexes
2021-02-15 17:20:41 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-02-15 17:20:41 0 [Note] InnoDB: Number of pools: 1
2021-02-15 17:20:41 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-02-15 17:20:41 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2021-02-15 17:20:41 0 [Note] InnoDB: Completed initialization of buffer pool
2021-02-15 17:20:42 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2021-02-15 17:20:42 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-02-15 17:20:42 0 [Note] InnoDB: Setting file 'F:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-02-15 17:20:42 0 [Note] InnoDB: File 'F:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2021-02-15 17:20:42 0 [Note] InnoDB: Waiting for purge to start
2021-02-15 17:20:42 0 [Note] InnoDB: 10.4.17 started; log sequence number 24762359; transaction id 126000
2021-02-15 17:20:42 0 [Note] InnoDB: Loading buffer pool(s) from F:\xampp\mysql\data\ib_buffer_pool
2021-02-15 17:20:42 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-02-15 17:20:42 0 [Note] InnoDB: Buffer pool(s) load completed at 210215 17:20:42
2021-02-15 17:20:42 0 [Note] Server socket created on IP: '::'.
InnoDB: using atomic writes.
2021-02-15 17:21:16 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2021-02-15 17:21:16 0 [Note] InnoDB: Uses event mutexes
2021-02-15 17:21:16 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-02-15 17:21:16 0 [Note] InnoDB: Number of pools: 1
2021-02-15 17:21:16 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-02-15 17:21:16 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2021-02-15 17:21:16 0 [Note] InnoDB: Completed initialization of buffer pool
2021-02-15 17:21:17 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2021-02-15 17:21:17 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-02-15 17:21:17 0 [Note] InnoDB: Setting file 'F:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-02-15 17:21:17 0 [Note] InnoDB: File 'F:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2021-02-15 17:21:17 0 [Note] InnoDB: Waiting for purge to start
2021-02-15 17:21:17 0 [Note] InnoDB: 10.4.17 started; log sequence number 24762393; transaction id 126000
2021-02-15 17:21:17 0 [Note] InnoDB: Loading buffer pool(s) from F:\xampp\mysql\data\ib_buffer_pool
2021-02-15 17:21:17 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-02-15 17:21:17 0 [Note] InnoDB: Buffer pool(s) load completed at 210215 17:21:17
2021-02-15 17:21:17 0 [Note] Server socket created on IP: '::'.
InnoDB: using atomic writes.


Nothing works.

What causes this problem and how can I fix it? if you need more info, let me know and I'll provide it.




I tired all recommendations from this post: viewtopic.php?f=16&t=80337
dtommy79
 
Posts: 12
Joined: 24. June 2008 21:43
XAMPP version: 8.0.1
Operating System: Windows 10

Re: MySQL shutdown unexpectedly with weird log files

Postby Altrea » 15. February 2021 19:56

Hi,

  • Open your folder "\xampp\mysql\data"
  • Delete the file "multi-master.info"
  • Delete all files beginning with "master-"
  • Delete all files beginning with "mysql_relay-bin-"
  • Delete all files beginning with "relay-log-"
  • Delete all files beginning with "ib_logfile"
  • Delete all files beginning with "aria_log."

Now try to start mariadb the normal way again.
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 10730
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 87 guests