mysql does not start - Xampp 7.4.9

[fknuefer1]

...have been using Xampp, on and off, for years and while I'm no expert, things have been pretty smooth in the past. Yesterday, after a few month break, some further work was to be done and everything appeared to be fine. Eventually xampp was closed (via the control panel) - and nothing untowards happened here either. When Xampp was restarted today however, apache ran, but mysql failed, ...repeatedly.
The port (3306) was free. This not withstanding, it was changed for mysql to 3308. Another try, ... no joy. I've checked permissions for the mysql folders, they are OK. Passwords didn't change. Xampp vers. 7.4.9 on Win 10.

Below the xampp-control log:
16:14:33 [main] Initializing Control Panel
16:14:33 [main] Windows Version: Enterprise 64-bit
16:14:33 [main] XAMPP Version: 7.4.9
16:14:33 [main] Control Panel Version: 3.2.4 [ Compiled: Jun 5th 2019 ]
16:14:33 [main] Running with Administrator rights - good!
16:14:33 [main] XAMPP Installation Directory: "e:\xampp\"
16:14:33 [main] Checking for prerequisites
16:14:35 [main] All prerequisites found
16:14:35 [main] Initializing Modules
16:14:35 [main] Starting Check-Timer
16:14:35 [main] Control Panel Ready
16:14:39 [Apache] Attempting to start Apache app...
16:14:39 [Apache] Status change detected: running
16:14:45 [mysql] Attempting to start MySQL app...
16:14:45 [mysql] Status change detected: running
16:14:48 [mysql] Status change detected: stopped
16:14:48 [mysql] Error: MySQL shutdown unexpectedly.
16:14:48 [mysql] This may be due to a blocked port, missing dependencies,
16:14:48 [mysql] improper privileges, a crash, or a shutdown by another method.
16:14:48 [mysql] Press the Logs button to view error logs and check
16:14:48 [mysql] the Windows Event Viewer for more clues
16:14:48 [mysql] If you need more help, copy and post this
16:14:48 [mysql] entire log window on the forums
16:15:21 [mysql] Attempting to start MySQL app...
16:15:21 [mysql] Status change detected: running
16:15:23 [mysql] Status change detected: stopped
16:15:23 [mysql] Error: MySQL shutdown unexpectedly.
16:15:23 [mysql] This may be due to a blocked port, missing dependencies,
16:15:23 [mysql] improper privileges, a crash, or a shutdown by another method.
16:15:23 [mysql] Press the Logs button to view error logs and check
16:15:23 [mysql] the Windows Event Viewer for more clues
16:15:23 [mysql] If you need more help, copy and post this
16:15:23 [mysql] entire log window on the forums
16:15:47 [Apache] Attempting to stop Apache (PID: 13800)
16:15:47 [Apache] Attempting to stop Apache (PID: 10848)
16:15:47 [Apache] Status change detected: stopped
16:15:52 [main] Deinitializing Modules
16:15:52 [main] Deinitializing Control Panel

Here the error log for mysql... I have no idea what is going on here, but clearly mysql is very sick:

Cannot find checkpoint record at LSN (1,0x5556)
2020-12-15 16:14:46 0 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
2020-12-15 16:14:46 0 [ERROR] Plugin 'Aria' init function returned error.
2020-12-15 16:14:46 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
InnoDB: using atomic writes.
2020-12-15 16:14:46 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-12-15 16:14:46 0 [Note] InnoDB: Uses event mutexes
2020-12-15 16:14:46 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-12-15 16:14:46 0 [Note] InnoDB: Number of pools: 1
2020-12-15 16:14:46 0 [Note] InnoDB: Using generic crc32 instructions
2020-12-15 16:14:46 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2020-12-15 16:14:46 0 [Note] InnoDB: Completed initialization of buffer pool
2020-12-15 16:14:46 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1399201
2020-12-15 16:14:47 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-12-15 16:14:47 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2020-12-15 16:14:47 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-12-15 16:14:47 0 [Note] InnoDB: Setting file 'E:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-12-15 16:14:47 0 [Note] InnoDB: File 'E:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2020-12-15 16:14:47 0 [Note] InnoDB: Waiting for purge to start
2020-12-15 16:14:47 0 [Note] InnoDB: 10.4.14 started; log sequence number 1399210; transaction id 811
2020-12-15 16:14:47 0 [Note] InnoDB: Loading buffer pool(s) from E:\xampp\mysql\data\ib_buffer_pool
2020-12-15 16:14:47 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-12-15 16:14:47 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2020-12-15 16:14:47 0 [ERROR] Failed to initialize plugins.
2020-12-15 16:14:47 0 [ERROR] Aborting
Cannot find checkpoint record at LSN (1,0x5556)
2020-12-15 16:15:21 0 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
2020-12-15 16:15:21 0 [ERROR] Plugin 'Aria' init function returned error.
2020-12-15 16:15:21 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
InnoDB: using atomic writes.
2020-12-15 16:15:21 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-12-15 16:15:21 0 [Note] InnoDB: Uses event mutexes
2020-12-15 16:15:21 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-12-15 16:15:21 0 [Note] InnoDB: Number of pools: 1
2020-12-15 16:15:21 0 [Note] InnoDB: Using generic crc32 instructions
2020-12-15 16:15:21 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2020-12-15 16:15:21 0 [Note] InnoDB: Completed initialization of buffer pool
2020-12-15 16:15:21 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-12-15 16:15:21 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-12-15 16:15:21 0 [Note] InnoDB: Setting file 'E:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-12-15 16:15:21 0 [Note] InnoDB: File 'E:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2020-12-15 16:15:21 0 [Note] InnoDB: Waiting for purge to start
2020-12-15 16:15:21 0 [Note] InnoDB: 10.4.14 started; log sequence number 1399219; transaction id 811
2020-12-15 16:15:21 0 [Note] InnoDB: Loading buffer pool(s) from E:\xampp\mysql\data\ib_buffer_pool
2020-12-15 16:15:21 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-12-15 16:15:21 0 [Note] InnoDB: Buffer pool(s) load completed at 201215 16:15:21
2020-12-15 16:15:21 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2020-12-15 16:15:21 0 [ERROR] Failed to initialize plugins.
2020-12-15 16:15:21 0 [ERROR] Aborting

Help would be greatly appreciated, as this is starting to eat into my life. Thanks!!

[Altrea]

2020-12-15 16:15:21 0 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
2020-12-15 16:15:21 0 [ERROR] Plugin 'Aria' init function returned error.
2020-12-15 16:15:21 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
InnoDB: using atomic writes

This is your issue. You need to check all aria tables like described in the message. Here is a step by step instruction:

1. Open cmd.
2. In cmd, go to xampp/mysql/data folder. In my case, I did the following cd C:\xampp\mysql\data
3. Run aria_chk -r in that directory for all .MAI tables in the mysql subfolder. In my case, ..\bin\aria_chk -r mysql\*.MAI
4. Delete all aria_log.######## files. They are present in the C:\xampp\mysql\data folder. I just renamed them for just in case (added old_ in the beginning of their names).
5. Start xampp again and it should be working.

Reference: https://stackoverflow.com/a/59411279

2020-12-15 16:15:21 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2020-12-15 16:15:21 0 [ERROR] Failed to initialize plugins.
2020-12-15 16:15:21 0 [ERROR] Aborting

That is a consequential error from the first one.

[fknuefer1]

Hi Altrea,

thanks for the input, it is really appreciated. I followed your advice. Unfortunately the issue has not been resolved... there is some change of behaviour of mysql at startup though, ... before running aria_chk, mysql would bail out immediately, now it persist for a couple of seconds and the port it openend is displayed within the Control Panel (which it wasn't before).

Running aria_chk gave, between all the recovering and fixing, some unpleasant feedback:

..\bin\aria_chk: Index is corrupted
aria_chk: error: 'mysql\db.MAI' doesn't have a correct index definition. You need to recreate it before you can do a repair

This is from the mysql_error.log:

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

So I assume there is also a problem at another level...

When the problem occured, There was just one new database (Omeka-s 3.0.1) in the data folder with a single new record in a few tables. If this situation is not saved, not much is lost, but as I don't understand what has been going on, I feel a wee bit insecure regarding future development, so to say.

Any idea where we go from here? Can I recreate the db.MAI index? How?

cheers, Fred

[Altrea]

Can I recreate the db.MAI index? How?

you could try to replace the db.MAI file with the backup in \xampp\mysql\backup\mysql\

When the problem occured, There was just one new database (Omeka-s 3.0.1) in the data folder with a single new record in a few tables. If this situation is not saved, not much is lost

i new fresh install is always an option for sure.

but as I don't understand what has been going on, I feel a wee bit insecure regarding future development, so to say.

There are a few issues reported here at this support board relating to the mariaDB versions, most of them corrupted databases.
We currently suppose this is a problem with the way XAMPP terminates the MariaDB process. There are two ways to get around this problem:

• register the Windows Service for MariaDB, that way the shutdown procedure for a clean shutdown is triggered by Windows.
• shutdown MariaDB by command line SHUTDOWN command

  Code: Select all

  mysqladmin.exe -u root shutdown