Page 1 of 1

Mysql shut down unexpectedly

PostPosted: 13. September 2019 16:38
by tejkaran
8:59:14 PM [mysql] Error: MySQL shutdown unexpectedly.
8:59:14 PM [mysql] This may be due to a blocked port, missing dependencies,
8:59:14 PM [mysql] improper privileges, a crash, or a shutdown by another method.
8:59:14 PM [mysql] Press the Logs button to view error logs and check
8:59:14 PM [mysql] the Windows Event Viewer for more clues
8:59:14 PM [mysql] If you need more help, copy and post this
8:59:14 PM [mysql] entire log window on the forums

Re: Mysql shut down unexpectedly

PostPosted: 17. September 2019 05:35
by alje
I have the same issue. im waiting for any resolution.

Re: Mysql shut down unexpectedly

PostPosted: 17. September 2019 05:53
by Altrea
There is no way to solve this because way more debug information is needed to identify the issue.
For example, what is the contents of the mysql_error.log?
What is the output if you start MariaDB as console command?

There are serious bugs in XAMPP versions containing MariaDB 10.3.X. If your XAMPP version uses one of these versions you should consider to reinstall a newer version of XAMPP as soon as possible.

Re: Mysql shut down unexpectedly

PostPosted: 17. September 2019 06:51
by alje
the same error log can be found here:

https://community.apachefriends.org/f/viewtopic.php?f=16&t=78491

Re: Mysql shut down unexpectedly

PostPosted: 17. September 2019 10:40
by Altrea
Are you absolutely sure? Did you compare each single line?

Re: Mysql shut down unexpectedly

PostPosted: 18. September 2019 01:28
by alje
I AM ABSOLUTELY SURE. This just happen all of a suden.

another new user also reported this weird issue yesterday.

Re: Mysql shut down unexpectedly

PostPosted: 18. September 2019 06:22
by Altrea
So you are thinking that Thread 1 and Thread 2 are of the same or similar issue?

Let's quickly analyse their logs.

Thread 1:
  • innodb_force_recovery is set to greater than 0, so obviously someone has changed that to try to restore the database
  • ib_buffer_pool file (which is a MariaDB system file) cannot get read, but that is only a NOTE and may not prevent MariaDB from starting.
  • There are no further warnings or errors that can help to analyze the issue. The next step would be to try to start mysqld as console command to be able to get current log entries.

Therad 2:
  • innodb_force_recovery is set to 0 as per defaut
  • ib_buffer_pool file can be load successfully
  • There is some serious error of InnoDB file .\dsolo\daftar.ibd (which is a user generated database file) cannot be load because OS error 71 (File not found).
  • So it seams that the database is corrupted and need to be manually restored. Probably data of this database is lost if no backup is present.

So, these issues are NOT the same. The only similarities are that both are using MariaDB 10.3.16 and MariaDB refuses to start.

Now back to your story. Without knowing your full logs nobody can identify your secific issue.

Re: Mysql shut down unexpectedly

PostPosted: 18. September 2019 08:35
by alje
2019-09-17 11:52:46 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-09-17 11:52:46 0 [Note] InnoDB: Uses event mutexes
2019-09-17 11:52:46 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-09-17 11:52:46 0 [Note] InnoDB: Number of pools: 1
2019-09-17 11:52:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-09-17 11:52:46 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2019-09-17 11:52:46 0 [Note] InnoDB: Completed initialization of buffer pool
2019-09-17 11:52:46 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-09-17 11:52:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-09-17 11:52:46 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-09-17 11:52:46 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2019-09-17 11:52:46 0 [Note] InnoDB: Waiting for purge to start
2019-09-17 11:52:46 0 [Note] InnoDB: 10.3.16 started; log sequence number 153901880; transaction id 102405
2019-09-17 11:52:46 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2019-09-17 11:52:46 0 [Note] InnoDB: Buffer pool(s) load completed at 190917 11:52:46
2019-09-17 11:52:47 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-09-17 11:52:47 0 [Note] Server socket created on IP: '::'.

Re: Mysql shut down unexpectedly

PostPosted: 18. September 2019 08:53
by Altrea
Your mysql_error.log does not contain any error message.
The opposite is the case. The last line indicates that MariaDB could get started successfully.

Please try to start MariaDB as console application.
This can be done by clicking the Shell button in the control panel and executing the following command
Code: Select all
mysqld --console


The now appearing messages can give more detail about the issue.
Just to be safe: Did you change anything in the configurations?
What exactly makes you think MariaDB cannot start successfully?