Update to XAMPP 8.1.12 Problems with Maria dB Start up

Alles, was MariaDB und MySQL betrifft, kann hier besprochen werden.

Update to XAMPP 8.1.12 Problems with Maria dB Start up

Postby rgaDawg » 03. December 2022 23:23

Win11 Pro on Dell 5820 Work Station (64RAM, i9 10 cores)
Issues started with update from XAMPP 8.1.6 --> XAMPP 8.1.12 package

I'm having anomalous problems with SQL start up from XAMPP Control Panel
Thanks for any help, my temporary workaround is to keep a "lastGood" copy of mysql DIR
The error logs point to Drive D (which is not on this system)
Issue : phpMyAdmin showing problems:

XAMPP CONTROL PANEL MESSAGE
3:46:21 PM [Apache] Attempting to start Apache app...
3:46:22 PM [Apache] Status change detected: running
3:46:24 PM [mysql] Attempting to start MySQL app...
3:46:24 PM [mysql] Status change detected: running
3:46:25 PM [mysql] Status change detected: stopped
3:46:25 PM [mysql] Error: MySQL shutdown unexpectedly.
3:46:25 PM [mysql] This may be due to a blocked port, missing dependencies,
3:46:25 PM [mysql] improper privileges, a crash, or a shutdown by another method.
3:46:25 PM [mysql] Press the Logs button to view error logs and check
3:46:25 PM [mysql] the Windows Event Viewer for more clues
3:46:25 PM [mysql] If you need more help, copy and post this
3:46:25 PM [mysql] entire log window on the forums


MARIA DB ERROR LOGS

mysql_error.log

======= This is a good start up on 12-02-2022

2022-12-02 17:16:00 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-12-02 17:16:00 0 [Note] InnoDB: Uses event mutexes
2022-12-02 17:16:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-12-02 17:16:00 0 [Note] InnoDB: Number of pools: 1
2022-12-02 17:16:00 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-12-02 17:16:00 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-12-02 17:16:00 0 [Note] InnoDB: Completed initialization of buffer pool
2022-12-02 17:16:00 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=346844
2022-12-02 17:16:01 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-12-02 17:16:01 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-12-02 17:16:01 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-12-02 17:16:01 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-12-02 17:16:01 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2022-12-02 17:16:01 0 [Note] InnoDB: Waiting for purge to start
2022-12-02 17:16:01 0 [Note] InnoDB: 10.4.27 started; log sequence number 346853; transaction id 437
2022-12-02 17:16:01 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2022-12-02 17:16:01 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-12-02 17:16:01 0 [Note] Server socket created on IP: '::'.

======= Then Server was shut down 12-02-2022, 11:50:00 PM
And there were no errors logged on shutdown for this day


======= This is a start up on 12-03-2022 where the errors occur

2022-12-03 15:46:24 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-12-03 15:46:24 0 [Note] InnoDB: Uses event mutexes
2022-12-03 15:46:24 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-12-03 15:46:24 0 [Note] InnoDB: Number of pools: 1
2022-12-03 15:46:24 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-12-03 15:46:24 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-12-03 15:46:24 0 [Note] InnoDB: Completed initialization of buffer pool
2022-12-03 15:46:24 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=353368
2022-12-03 15:46:24 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-12-03 15:46:24 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-12-03 15:46:24 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-12-03 15:46:24 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-12-03 15:46:24 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2022-12-03 15:46:24 0 [Note] InnoDB: Waiting for purge to start
2022-12-03 15:46:24 0 [Note] InnoDB: 10.4.27 started; log sequence number 353377; transaction id 507
2022-12-03 15:46:24 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2022-12-03 15:46:24 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-12-03 15:46:24 0 [Note] Server socket created on IP: '::'.

======= error messages from bad start up

2022-12-03 15:46:24 0x1828 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6154
InnoDB: Failing assertion: slot
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
2022-12-03 15:46:24 0x415c InnoDB: Assertion failure in file D:\winx64-packages\build\src\stor221203 15:46:24 [ERROR] mysqld got exception 0x80000003 ;
aThis could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

gTo report this bug, see https://mariadb.com/kb/en/reporting-bugs

e\inWe will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

nServer version: 10.4.27-MariaDB
okey_buffer_size=16777216
bread_buffer_size=262144
amax_used_connections=0
smax_threads=65537
ethread_count=6
\It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20302 K bytes of memory
osHope that's ok; if not, decrease some variables in the equation.

\Thread pointer: 0x0
oAttempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
s0file.cc line 6154
InnoDB: Failing assertion: slot
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
2022-12-
rgaDawg
 
Posts: 5
Joined: 03. December 2022 23:08
XAMPP version: 8.1.12
Operating System: Win11 Pro, Dell 5820 WorkSt

Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 16 guests