Apache Friends Support Forum

by **amy k** » 01. August 2022 15:40

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

i almost tried all the solutions on web. please do help me with it Thank you

by **Altrea** » 01. August 2022 19:20

Don't try random solutions, start debugging the real cause of this issue.

Try to start MariaDB as console application and tell us what it responses. To do so, please:

Open a new XAMPP Shell by clicking the Shell Button in your control panel
type in the following command
Code: Select all
mysqld --defaults-file=mysql\bin\my.ini --standalone --console
copy us the response of the console

by **cruzzyboy136** » 06. October 2022 17:30

# mysqld --defaults-file=mysql\bin\my.ini --standalone --console
2022-10-06 17:28:20 0 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2022-10-06 17:28:20 0 [Note] mysqld (mysqld 10.4.21-MariaDB) starting as process 11276 ...
2022-10-06 17:28:20 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-10-06 17:28:20 0 [Note] InnoDB: Uses event mutexes
2022-10-06 17:28:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-10-06 17:28:20 0 [Note] InnoDB: Number of pools: 1
2022-10-06 17:28:20 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-10-06 17:28:20 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-10-06 17:28:20 0 [Note] InnoDB: Completed initialization of buffer pool
2022-10-06 17:28:20 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-10-06 17:28:20 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-10-06 17:28:20 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-10-06 17:28:20 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2022-10-06 17:28:20 0 [Note] InnoDB: Waiting for purge to start
2022-10-06 17:28:20 0 [Note] InnoDB: 10.4.21 started; log sequence number 169503778; transaction id 232806
2022-10-06 17:28:20 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2022-10-06 17:28:20 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-10-06 17:28:20 0 [Note] Server socket created on IP: '::'.
2022-10-06 17:28:20 0 [Note] InnoDB: Buffer pool(s) load completed at 221006 17:28:20
2022-10-06 17:28:20 7 [Note] Reading Master_info: 'master-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020reading@0020of@0020all@0020master_info@0020entries@0020succeeded@000d.info' Relay_info:'relay-log-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020reading@0020of@0020all@0020master_info@0020entries@0020succeeded@000d.info'
2022-10-06 17:28:20 7 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MariaDB server acts as a replica and has its hostname changed. Please use '--log-basename=#' or '--relay-log=mysql-relay-bin' to avoid this problem.
2022-10-06 17:28:20 7 [Note] Initialized Master_info from 'master-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020reading@0020of@0020all@0020master_info@0020entries@0020succeeded@000d.info'
2022-10-06 17:28:20 7 [Note] Added new Master_info '2022-05-11 18:23:18 0 [Note] Reading of all Master_info entries succ' to hash table
': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4ntries succeeded
': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
': Slave I/O thread killed while connecting to master:18 0 [Note] Reading of all Master_info entries succeeded
': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '.\mysql-relay-bin-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020reading@0020of@0020all@0020master_info@0020entries@0020succeeded@000d.000001' position: 4
2022-10-06 17:28:20 7 [Note] Started replication for '2022-05-11 18:23:18 0 [Note] Reading of all Master_info entries su'ceeded
': Slave I/O thread exiting, read up to log 'FIRST', position 4e] Reading of all Master_info entries succeeded
2022-10-06 17:28:20 7 [Note] Reading Master_info: 'master-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@000d.info' Relay_info:'relay-log-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@000d.info'
': master was :3306 8 [Note] Master '2022-05-11 18:23:18 0 [Note] Reading of all Master_info entries succeeded
2022-10-06 17:28:20 7 [Note] Initialized Master_info from 'master-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@000d.info'
' to hash table8:20 7 [Note] Added new Master_info '2022-05-11 18:23:18 0 [Note] Added new Master_info '' to hash table
': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 hash table
': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
2022-10-06 17:28:20 7 [Note] Started replication for '2022-05-11 18:23:18 0 [Note] Added new Master_info '' to hash tabl'
': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '.\mysql-relay-bin-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@000d.000001' position: 4
': Slave I/O thread killed while connecting to master3:18 0 [Note] Added new Master_info '' to hash table
2022-10-06 17:28:20 7 [Note] Reading Master_info: 'master-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020c@003a@005cxampp@005cmysql@005cbin@005cmysqld@002eexe@003a@0020ready@0020for@0020connections@002e@000d.info' Relay_info:'relay-log-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020c@003a@005cxampp@005cmysql@005cbin@005cmysqld@002eexe@003a@0020ready@0020for@0020connections@002e@000d.info'
': Slave I/O thread exiting, read up to log 'FIRST', position 4te] Added new Master_info '' to hash table
': master was :3306 10 [Note] Master '2022-05-11 18:23:18 0 [Note] Added new Master_info '' to hash table
2022-10-06 17:28:20 7 [Note] Initialized Master_info from 'master-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020c@003a@005cxampp@005cmysql@005cbin@005cmysqld@002eexe@003a@0020ready@0020for@0020connections@002e@000d.info'
2022-10-06 17:28:20 7 [Note] Added new Master_info '2022-05-11 18:23:18 0 [Note] c:\xampp\mysql\bin\mysqld.exe: ready fo' to hash table
': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4xe: ready for connections.2022-10-06 17:28:20 7 [Note] Started replication for '2022-05-11 18:23:18 0 [Note] c:\xampp\mysql\bin\mysqld.exe: ready 'or connections.
2022-10-06 17:28:20 12 [ERROR] Master '2022-05-11 18:23:18 0 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '.\mysql-relay-bin-2022@002d05@002d11@002018@003a23@003a18@00200@0020@005bnote@005d@0020c@003a@005cxampp@005cmysql@005cbin@005cmysqld@002eexe@003a@0020ready@0020for@0020connections@002e@000d.000001' position: 4
2022-10-06 17:28:20 7 [Note] Reading Master_info: 'master-version@003a@0020@002710@002e4@002e21@002dmariadb@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d.info' Relay_info:'relay-log-version@003a@0020@002710@002e4@002e21@002dmariadb@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d.info'
': Slave I/O thread killed while connecting to master3:18 0 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.': Slave I/O thread exiting, read up to log 'FIRST', position 4te] c:\xampp\mysql\bin\mysqld.exe: ready for connections.': master was :3306 12 [Note] Master '2022-05-11 18:23:18 0 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.2022-10-06 17:28:20 7 [ERROR] log .\mysql-relay-bin-version@003a@0020@002710@002e4@002e21@002dmariadb@0027@0020@0020sock listed in the index, but failed to statreplication to master '@:3306' in log '' at position 4
2022-10-06 17:28:20 7 [ERROR] Error counting relay log space
2022-10-06 17:28:20 7 [ERROR] Initialized Master_info from 'master-version@003a@0020@002710@002e4@002e21@002dmariadb@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d.info' failed
2022-10-06 17:28:20 7 [Note] Added new Master_info 'Version: '10.4.21-MariaDB' socket: '' port: 3306 mariadb.org bina' to hash table
2022-10-06 17:28:20 0 [Warning] Reading of some Master_info entries failed
2022-10-06 17:28:20 0 [ERROR] Failed to initialize multi master structures
2022-10-06 17:28:20 0 [ERROR] Aborting
Warning: Memory not freed: 16864

by **theking2** » 07. October 2022 19:30

The reason is the way mariadb is shutdown by the control panel. Install mariadb as service andvthis problem might very likely not appear.

by **huseintaha** » 14. December 2022 04:18

Altrea wrote:Don't try random solutions, start debugging the real cause of this issue.

Try to start MariaDB as console application and tell us what it responses. To do so, please:
Open a new XAMPP Shell by clicking the Shell Button in your control panel
type in the following command
Code: Select all
mysqld --defaults-file=mysql\bin\my.ini --standalone --console
copy us the response of the console

i make this line in shell still error found
my sw xampp at win10

by **Froosh** » 14. December 2022 14:56

That is really very little information for anyone to work with. You do not indicate what error you are trying to resolve, or even the XAMPP version. Provide details and you will likely receive advice.

by **eldooM** » 06. January 2023 17:13

Hi Apache Friends,
I have to admit, that recently a similar incident took place on my computer as well:
Besides the Hope that any of the Apache Friends can fix my problem, I would like to get in discussion with some serious aspects of using xampp.
Is it really such instable to use xampp under quiet normal circumstances to dig into trouble with innoDB such deep ?
And when, how can I avoid digging in such deep holes again ?
What do you think, my dear Apache friend, should I know about the processes around the mysql services, the interface to the operating system and things like that on this system level ?
As I find in the forum, issues like that went into the 1000.
If something is so critical in using xampp on window can you offer a description what might be helpfull to avoid such critical pathes ?

nevertheless please help me out of my current misery.
I use
windows 11
XAMPP Version 8.1.12
I run Mariadb in context with Moodle
After the incident I run mysqld in shell context as I found the command in this forum:

C:\myApps\xampp\htdocs\Moodle-4.1\server>.\mysql\bin\mysqld --defaults-file=mysql\bin\my.ini --standalone --console
2023-01-06 11:57:19 0 [Note] .\mysql\bin\mysqld (mysqld 10.4.27-MariaDB) starting as process 11296 ...
2023-01-06 11:57:19 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-01-06 11:57:19 0 [Note] InnoDB: Uses event mutexes
2023-01-06 11:57:19 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-01-06 11:57:19 0 [Note] InnoDB: Number of pools: 1
2023-01-06 11:57:19 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-01-06 11:57:19 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2023-01-06 11:57:19 0 [Note] InnoDB: Completed initialization of buffer pool
2023-01-06 11:57:19 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=20673206
2023-01-06 11:57:19 0 [Note] InnoDB: Starting final batch to recover 3 pages from redo log.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__bookmark.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__bookmark``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__bookmark` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__central_columns.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__central_columns``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__central_columns` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__column_info.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__column_info``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__column_info` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__designer_settings.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__designer_settings``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__designer_settings` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__export_templates.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__export_templates``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__export_templates` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__favorite.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__favorite``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__favorite` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__history.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__history``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__history` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__navigationhiding.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__navigationhiding``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__navigationhiding` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__pdf_pages.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__pdf_pages``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__pdf_pages` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__recent.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__recent``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__recent` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__relation.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__relation``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__relation` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__savedsearches.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__savedsearches``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__savedsearches` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__table_coords.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__table_coords``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__table_coords` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__table_info.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__table_info``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__table_info` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__table_uiprefs.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__table_uiprefs``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__table_uiprefs` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__tracking.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__tracking``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__tracking` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__userconfig.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__userconfig``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__userconfig` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__usergroups.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__usergroups``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__usergroups` because it could not be opened.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-01-06 11:57:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-01-06 11:57:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\phpmyadmin\pma__users.ibd' OS error: 203
2023-01-06 11:57:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-01-06 11:57:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-01-06 11:57:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``phpmyadmin`.`pma__users``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-01-06 11:57:23 0 [Warning] InnoDB: Ignoring tablespace for `phpmyadmin`.`pma__users` because it could not be opened.
2023-01-06 11:57:23 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-01-06 11:57:23 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-01-06 11:57:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-01-06 11:57:23 0 [Note] InnoDB: Setting file 'C:\myApps\xampp\htdocs\Moodle-4.1\server\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-01-06 11:57:23 0 [Note] InnoDB: File 'C:\myApps\xampp\htdocs\Moodle-4.1\server\mysql\data\ibtmp1' size is now 12 MB.
2023-01-06 11:57:23 0 [Note] InnoDB: Waiting for purge to start
2023-01-06 11:57:23 0 [Note] InnoDB: 10.4.27 started; log sequence number 20675350; transaction id 37124
2023-01-06 11:57:23 0 [Note] InnoDB: Loading buffer pool(s) from C:\myApps\xampp\htdocs\Moodle-4.1\server\mysql\data\ib_buffer_pool
2023-01-06 11:57:23 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-01-06 11:57:23 0 [ERROR] InnoDB: Expected tablespace id 2 but found 4294967294 in the file .\mysql\innodb_index_stats.ibd
2023-01-06 11:57:23 0 [Note] InnoDB: trying to read page [page id: space=2, page number=0] in the background in a non-existing or being-dropped tablespace
2023-01-06 11:57:23 0 [ERROR] InnoDB: Expected tablespace id 2 but found 4294967294 in the file .\mysql\innodb_index_stats.ibd
2023-01-06 11:57:23 0 [Note] InnoDB: trying to read page [page id: space=2, page number=1] in the background in a non-existing or being-dropped tablespace
2023-01-06 11:57:23 0 [ERROR] InnoDB: Expected tablespace id 2 but found 4294967294 in the file .\mysql\innodb_index_stats.ibd
2023-01-06 11:57:23 0 [Note] InnoDB: trying to read page [page id: space=2, page number=2] in the background in a non-existing or being-dropped tablespace
2023-01-06 11:57:23 0 [ERROR] InnoDB: Expected tablespace id 2 but found 4294967294 in the file .\mysql\innodb_index_stats.ibd
2023-01-06 11:57:23 0 [Note] InnoDB: trying to read page [page id: space=2, page number=3] in the background in a non-existing or being-dropped tablespace
2023-01-06 11:57:23 0 [Note] InnoDB: Buffer pool(s) load completed at 230106 11:57:23
2023-01-06 11:57:23 0 [Note] Server socket created on IP: '::'.
2023-01-06 11:57:23 6 [ERROR] InnoDB: Expected tablespace id 2 but found 4294967294 in the file .\mysql\innodb_index_stats.ibd
2023-01-06 11:57:23 6 [ERROR] InnoDB: Expected tablespace id 2 but found 4294967294 in the file .\mysql\innodb_index_stats.ibd
2023-01-06 11:57:23 6 [ERROR] InnoDB: Table `mysql`.`innodb_index_stats` is corrupted. Please drop the table and recreate.
2023-01-06 11:57:23 0x5aec InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\pars\pars0pars.cc line 772
InnoDB: Failing assertion: sym_node->table != NULL
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.
230106 11:57:23 [ERROR] mysqld got exception 0x80000003 ;
This 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.

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

We 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.

Server version: 10.4.27-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_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
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1d4f874af58
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!?append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV12@QEBD_K@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!strmov()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV12@QEBD_K@Z()
mysqld.exe!?append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV12@QEBD_K@Z()
mysqld.exe!?ha_open@handler@@QEAAHPEAUTABLE@@PEBDHIPEAUst_mem_root@@PEAV?$List@VString@@@@@Z()
mysqld.exe!?open_table_from_share@@YA?AW4open_frm_error@@PEAVTHD@@PEAUTABLE_SHARE@@PEBUst_mysql_const_lex_string@@IIIPEAUTABLE@@_NPEAV?$List@VString@@@@@Z()
mysqld.exe!?open_table@@YA_NPEAVTHD@@PEAUTABLE_LIST@@PEAVOpen_table_context@@@Z()
mysqld.exe!?open_and_lock_tables@@YA_NPEAVTHD@@AEBUDDL_options_st@@PEAUTABLE_LIST@@_NIPEAVPrelocking_strategy@@@Z()
mysqld.exe!?open_tables@@YA_NPEAVTHD@@AEBUDDL_options_st@@PEAPEAUTABLE_LIST@@PEAIIPEAVPrelocking_strategy@@@Z()
mysqld.exe!?open_and_lock_tables@@YA_NPEAVTHD@@AEBUDDL_options_st@@PEAUTABLE_LIST@@_NIPEAVPrelocking_strategy@@@Z()
mysqld.exe!?rpl_load_gtid_slave_state@@YAHPEAVTHD@@@Z()
mysqld.exe!?is_until_satisfied@Relay_log_info@@QEAA_NPEAVLog_event@@@Z()
mysqld.exe!?rpl_load_gtid_slave_state@@YAHPEAVTHD@@@Z()
mysqld.exe!?rpl_load_gtid_slave_state@@YAHPEAVTHD@@@Z()
mysqld.exe!?apply_event_and_update_pos_for_parallel@@YAHPEAVLog_event@@PEAVTHD@@PEAUrpl_group_info@@@Z()
mysqld.exe!handle_manager()
mysqld.exe!pthread_join()
ucrtbase.dll!_recalloc()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0):
Connection ID (thread ID): 6
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\myApps\xampp\htdocs\Moodle-4.1\server\mysql\data\
Minidump written to C:\myApps\xampp\htdocs\Moodle-4.1\server\mysql\data\mysqld.dmp

C:\myApps\xampp\htdocs\Moodle-4.1\server>

by **huseintaha** » 12. February 2023 20:04

Froosh wrote: after i run command in shall prombet
mysqld --defaults-file=mysql\bin\my.ini --standalone --console
this error is raise.

pc@DESKTOP-0SR7FM4 d:\xampp
# mysqld --defaults-file=mysql\bin\my.ini --standalone --console
2023-02-12 20:55:44 0 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2023-02-12 20:55:44 0 [Note] mysqld (mysqld 10.3.16-MariaDB) starting as process 13464 ...
2023-02-12 20:55:44 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-02-12 20:55:44 0 [Note] InnoDB: Uses event mutexes
2023-02-12 20:55:44 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-02-12 20:55:44 0 [Note] InnoDB: Number of pools: 1
2023-02-12 20:55:44 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-02-12 20:55:44 0 [Note] InnoDB: Initializing buffer pool, total size = 10M, instances = 1, chunk size = 10M
2023-02-12 20:55:44 0 [Note] InnoDB: Completed initialization of buffer pool
2023-02-12 20:55:44 0 [ERROR] InnoDB: Page [page id: space=0, page number=4] log sequence number 17043745 is in the future! Current system log sequence number 15919602.
2023-02-12 20:55:44 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-02-12 20:55:44 0 [ERROR] InnoDB: Page [page id: space=0, page number=11] log sequence number 20611167 is in the future! Current system log sequence number 15919602.
2023-02-12 20:55:44 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2023-02-12 20:55:44 0 [ERROR] InnoDB: Page [page id: space=0, page number=440] log sequence number 16300021 is in the future! Current system log sequence number 15919602.

': Slave I/O thread killed while connecting to master7:10 0 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.': Slave I/O thread exiting, read up to log 'FIRST', position 4te] d:\xampp\mysql\bin\mysqld.exe: ready for connections.2023-02-12 20:55:47 7 [Note] Initialized Master_info from 'master-version@003a@0020@002710@002e3@002e16@002dmariadb@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d.info'
2023-02-12 20:55:47 7 [ERROR] Connection 'Version: '10.3.16-MariaDB' socket: '' port: 3306 mariadb.org binary distrib' conflicts with existing connection 'Version: '10.3.16-MariaDB' socket: '' port: 3306 mariadb.org binary distributio'
2023-02-12 20:55:47 7 [Note] Reading Master_info: 'master-2023@002d02@002d12@0020@00200@003a57@003a10@002014@0020@005bnote@005d@0020master@0020@0027version@003a@0020@002710@002e3@002e16@002dmariadb@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d@0027@003a@0020slave@0020i@002fo@0020thread@0020exiting@002.info' Relay_info:'relay-log-2023@002d02@002d12@0020@00200@003a57@003a10@002014@0020@005bnote@005d@0020master@0020@0027version@003a@0020@002710@002e3@002e16@002dmariadb@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d@0027@003a@0020slave@0020i@002fo@0020thread@0020exiting@002.info'
2023-02-12 20:55:47 7 [ERROR] Failed to create a new master info file (file 'D:\XAMPP\mysql\data\master-2023@002d02@002d12@0020@00200@003a57@003a10@002014@0020@005bnote@005d@0020master@0020@0027version@003a@0020@002710@002e3@002e16@002dmariadb@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d@0027@003a@0020slave@0020i@002fo@0020thread@0020exiting@002.info', errno 2)
2023-02-12 20:55:47 7 [ERROR] Initialized Master_info from 'master-2023@002d02@002d12@0020@00200@003a57@003a10@002014@0020@005bnote@005d@0020master@0020@0027version@003a@0020@002710@002e3@002e16@002dmariadb@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d@0027@003a@0020slave@0020i@002fo@0020thread@0020exiting@002.info' failed
2023-02-12 20:55:47 7 [Note] Added new Master_info '2023-02-12 0:57:10 14 [Note] Master 'Version: '10.3.16-MariaDB' so' to hash tableread exiting, read up to log 'FIRST', position 4
2023-02-12 20:55:47 0 [Warning] Reading of some Master_info entries failed
2023-02-12 20:55:47 0 [ERROR] Failed to initialize multi master structures
2023-02-12 20:55:47 0 [ERROR] Aborting

pc@DESKTOP-0SR7FM4 d:\xampp
#

Apache Friends Support Forum

Error: MySQL shutdown unexpectedly

Error: MySQL shutdown unexpectedly

Re: Error: MySQL shutdown unexpectedly

Re: Error: MySQL shutdown unexpectedly

Re: Error: MySQL shutdown unexpectedly

Re: Error: MySQL shutdown unexpectedly

Re: Error: MySQL shutdown unexpectedly

Re: Error: MySQL shutdown unexpectedly

Re: Error: MySQL shutdown unexpectedly

Who is online