Mysql lässt sich nicht mehr starten

Irgendwelche Probleme mit XAMPP für Windows? Dann ist hier genau der richtige Ort um nachzufragen.

Mysql lässt sich nicht mehr starten

Postby olaf.nagel » 02. July 2023 08:00

Hallo liebe Leute,

ich habe eine Weile nichts gemacht ausser die normalen Updates MS. Jetzt stelle ich fest das sich mysql nicht mehr starten lässt die logfile zeigt folgendes Problem an:
InnoDB:

2023-07-02 6:35:58 0 [Note] Mutexes and rw_locks use Windows interlocked functions
2023-07-02 6:35:58 0 [Note] InnoDB: Uses event mutexes
2023-07-02 6:35:58 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-07-02 6:35:58 0 [Note] InnoDB: Number of pools: 1
2023-07-02 6:35:58 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-07-02 6:35:58 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-07-02 6:35:58 0 [Note] InnoDB: Completed initialization of buffer pool
2023-07-02 6:36:00 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-07-02 6:36:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-07-02 6:36:00 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-07-02 6:36:00 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-07-02 6:36:00 0 [Note] InnoDB: Waiting for purge to start
2023-07-02 6:36:00 0 [Note] InnoDB: 10.4.21 started; log sequence number 5464498252; transaction id 40591623
2023-07-02 6:36:00 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-07-02 6:36:00 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-07-02 6:36:00 0 [Note] InnoDB: Buffer pool(s) load completed at 230702 6:36:00
2023-07-02 6:36:00 0 [Note] Server socket created on IP: '::'.

nun ist mein Wissen wohl nicht ausreichend um den Fehler zu beheben. Was früher geholfen hat wie z.B.: Prot ändern hat nicht geholfen.
Kann mir jemand helfen?
Ich möchte eigentlich nur eine Sicherung durchführen und die neue Xampp installieren.

Vielen Dank im Voraus
olaf.nagel
 
Posts: 7
Joined: 04. March 2022 10:34
XAMPP version: v3.3.0
Operating System: win10

Re: Mysql lässt sich nicht mehr starten

Postby Nobbie » 02. July 2023 11:15

Da ist keine einzige Fehlermeldung bei, nicht einmal eine Warnung. Alles nur "Note", das ist nur ein Hinweis, eine Notiz.
Nobbie
 
Posts: 13176
Joined: 09. March 2008 13:04

Re: Mysql lässt sich nicht mehr starten

Postby Altrea » 02. July 2023 12:41

Hi,

Zuerst einmal müssen wir klären, welche Art von Problem MariaDB wirklich hat.
Versuche dazu bitte mal MariaDB als Konsolenanwendung zu starten.

  • Öffne eine neue XAMPP Shell per Klick auf den Shell Knopf im XAMPP control panel
  • gebe folgendes command ein
    Code: Select all
    mysqld --defaults-file=mysql\bin\my.ini --standalone --console
  • kopiere die Ausgabe davon hier ins Forum
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: 11933
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 11 Pro x64

Re: Mysql lässt sich nicht mehr starten

Postby olaf.nagel » 02. July 2023 14:17

Shell gestartet und das ist die Anzeige:

Setting environment for using XAMPP for Windows.
HP@DESKTOP-SG4C4O2 c:\xampp
# mysqld --defaults-file=mysql\bin\my.ini --standalone --console
2023-07-02 15:20:08 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-07-02 15:20:08 0 [Note] mysqld (mysqld 10.4.21-MariaDB) starting as process 10272 ...
2023-07-02 15:20:08 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-07-02 15:20:08 0 [Note] InnoDB: Uses event mutexes
2023-07-02 15:20:08 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-07-02 15:20:08 0 [Note] InnoDB: Number of pools: 1
2023-07-02 15:20:08 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-07-02 15:20:08 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-07-02 15:20:08 0 [Note] InnoDB: Completed initialization of buffer pool
2023-07-02 15:20:09 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-07-02 15:20:09 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-07-02 15:20:09 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-07-02 15:20:09 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-07-02 15:20:09 0 [Note] InnoDB: Waiting for purge to start
2023-07-02 15:20:09 0 [Note] InnoDB: 10.4.21 started; log sequence number 5464498270; transaction id 40591623
2023-07-02 15:20:09 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-07-02 15:20:09 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-07-02 15:20:09 0 [Note] InnoDB: Buffer pool(s) load completed at 230702 15:20:09
2023-07-02 15:20:09 0 [Note] Server socket created on IP: '::'.
2023-07-02 15:20:09 7 [Note] Reading Master_info: 'master-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020reading@0020of@0020all@0020master_info@0020entries@0020succeeded@000d.info' Relay_info:'relay-log-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020reading@0020of@0020all@0020master_info@0020entries@0020succeeded@000d.info'
2023-07-02 15:20:09 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.
2023-07-02 15:20:09 7 [Note] Initialized Master_info from 'master-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020reading@0020of@0020all@0020master_info@0020entries@0020succeeded@000d.info'
2023-07-02 15:20:09 7 [Note] Added new Master_info '2023-05-27 20:47:33 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
2023-07-02 15:20:09 7 [Note] Started replication for '2023-05-27 20:47:33 0 [Note] Reading of all Master_info entries su'ceeded
': Slave I/O thread killed while connecting to master:33 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-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020reading@0020of@0020all@0020master_info@0020entries@0020succeeded@000d.000057' position: 4
2023-07-02 15:20:09 7 [Note] Reading Master_info: 'master-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@000d.info' Relay_info:'relay-log-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@000d.info'
': Slave I/O thread exiting, read up to log 'FIRST', position 4e] Reading of all Master_info entries succeeded
': master was :3306 8 [Note] Master '2023-05-27 20:47:33 0 [Note] Reading of all Master_info entries succeeded
2023-07-02 15:20:09 7 [ERROR] log 2023-06-17 15:27:38 7 [Note] Initialized Master_info from 'master-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@ listed in the index, but failed to stat
2023-07-02 15:20:09 7 [ERROR] Error counting relay log space
2023-07-02 15:20:09 7 [ERROR] Initialized Master_info from 'master-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020added@0020new@0020master_info@0020@0027@0027@0020to@0020hash@0020table@000d.info' failed
' to hash table0:09 7 [Note] Added new Master_info '2023-05-27 20:47:33 0 [Note] Added new Master_info '' to hash table
2023-07-02 15:20:09 7 [Note] Reading Master_info: 'master-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020c@003a@005cxampp@005cmysql@005cbin@005cmysqld@002eexe@003a@0020ready@0020for@0020connections@002e@000d.info' Relay_info:'relay-log-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020c@003a@005cxampp@005cmysql@005cbin@005cmysqld@002eexe@003a@0020ready@0020for@0020connections@002e@000d.info'
2023-07-02 15:20:09 7 [Note] Initialized Master_info from 'master-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020c@003a@005cxampp@005cmysql@005cbin@005cmysqld@002eexe@003a@0020ready@0020for@0020connections@002e@000d.info'
2023-07-02 15:20:09 7 [Note] Added new Master_info '2023-05-27 20:47:33 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.
2023-07-02 15:20:09 10 [ERROR] Master '2023-05-27 20:47:33 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
2023-07-02 15:20:09 7 [Note] Started replication for '2023-05-27 20:47:33 0 [Note] c:\xampp\mysql\bin\mysqld.exe: ready 'or connections.
': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '.\mysql-relay-bin-2023@002d05@002d27@002020@003a47@003a33@00200@0020@005bnote@005d@0020c@003a@005cxampp@005cmysql@005cbin@005cmysqld@002eexe@003a@0020ready@0020for@0020connections@002e@000d.000001' position: 4
': Slave I/O thread killed while connecting to master7:33 0 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
2023-07-02 15:20:09 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 exiting, read up to log 'FIRST', position 4te] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
': master was :3306 10 [Note] Master '2023-05-27 20:47:33 0 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
2023-07-02 15:20:10 7 [Note] 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'
2023-07-02 15:20:10 7 [Note] Added new Master_info 'Version: '10.4.21-MariaDB' socket: '' port: 3306 mariadb.org bina' to hash table
2023-07-02 15:20:10 12 [Note] Master 'Version: '10.4.21-MariaDB' socket: '' port: 3306 mariadb.org binary distributio': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4
2023-07-02 15:20:10 12 [ERROR] Master 'Version: '10.4.21-MariaDB' socket: '' port: 3306 mariadb.org binary distributi': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593
2023-07-02 15:20:10 7 [Note] Started replication for 'Version: '10.4.21-MariaDB' socket: '' port: 3306 mariadb.org bi'ary distribution
2023-07-02 15:20:10 12 [Note] Master 'Version: '10.4.21-MariaDB' socket: '' port: 3306 mariadb.org binary distributio': Slave I/O thread killed while connecting to master
2023-07-02 15:20:10 13 [Note] Master 'Version: '10.4.21-MariaDB' socket: '' port: 3306 mariadb.org binary distributio': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log '.\mysql-relay-bin-version@003a@0020@002710@002e4@002e21@002dmariadb@0027@0020@0020socket@003a@0020@0027@0027@0020@0020port@003a@00203306@0020@0020mariadb@002eorg@0020binary@0020distribution@000d.000001' position: 4
2023-07-02 15:20:10 0 [Warning] Reading of some Master_info entries failed
2023-07-02 15:20:10 12 [Note] Master 'Version: '10.4.21-MariaDB' socket: '' port: 3306 mariadb.org binary distributio': Slave I/O thread exiting, read up to log 'FIRST', position 4
2023-07-02 15:20:10 0 [ERROR] Failed to initialize multi master structures
2023-07-02 15:20:10 12 [Note] Master 'Version: '10.4.21-MariaDB' socket: '' port: 3306 mariadb.org binary distributio': master was :3306
2023-07-02 15:20:10 0 [ERROR] Aborting
Warning: Memory not freed: 16832

HP@DESKTOP-SG4C4O2 c:\xampp
#
olaf.nagel
 
Posts: 7
Joined: 04. March 2022 10:34
XAMPP version: v3.3.0
Operating System: win10

Re: Mysql lässt sich nicht mehr starten

Postby Altrea » 02. July 2023 14:55

Versuche bitte mal folgendes. Es löst in der Regel das multi-master Problem:

  • Öffne den Ordner "\xampp\mysql\data"
  • Lösche die Datei "multi-master.info"
  • Lösche alle Dateien, beginnend mit "master-"
  • Lösche alle Dateien, beginnend mit "mysql_relay-bin-"
  • Lösche alle Dateien, beginnend mit "relay-log-"

Versuche nun mariaDB normal wieder zu starten.
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: 11933
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 11 Pro x64

Re: Mysql lässt sich nicht mehr starten

Postby olaf.nagel » 02. July 2023 18:40

danke für die Hilfe.
wie kann ich das in Zukunft verhindern?
olaf.nagel
 
Posts: 7
Joined: 04. March 2022 10:34
XAMPP version: v3.3.0
Operating System: win10

Re: Mysql lässt sich nicht mehr starten

Postby Altrea » 02. July 2023 19:12

Die Art und Weise wie XAMPP MariaDB beendet ist nicht kontrolliert.
MariaDB wird sauberer beendet, wenn du für diese Komponente einen Windows Dienst registrierst.
Dieser Dienst wird dann auch automatisch vom XAMPP control panel verwendet.
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: 11933
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 11 Pro x64

Re: Mysql lässt sich nicht mehr starten

Postby photogeist » 21. September 2023 13:33

Ich habe das gleiche Problem, seit ich auf dem neuen Notebook mit Windows 11 das XAMPP installiert habe. ein paar mal läuft es wunderbar, dann Absturz direkt nach Start von Datenbank.
Da der Notebook immer heruntergefahren werden muss, bitte um Anleitung, wie man die MariaDB als Windows-Dienst registriert.
Zur Info: Auf dem vorigen Laptop mit Windows 10 ist XAMPP mit fast täglichem an- und ausmachen via Konsole IMMER gelaufen OHNE irgendwelche Probleme der DB. Was also hat sich von Win 10 zu Win 11 geändert?
photogeist
 
Posts: 2
Joined: 21. September 2023 08:39
XAMPP version: 3.3.0
Operating System: Windows 11

Re: Mysql lässt sich nicht mehr starten

Postby Nobbie » 21. September 2023 19:11

photogeist wrote:Da der Notebook immer heruntergefahren werden muss, bitte um Anleitung, wie man die MariaDB als Windows-Dienst registriert.


"Anleitung" ist weit zu hoch gegriffen - im Xampp Controlcenter ein Kreuzchen setzen in dem entsprechenden Kästchen vor MySQL (MariaDB), ob MySQL als Dienst gestartet werden soll.

photogeist wrote:Was also hat sich von Win 10 zu Win 11 geändert?


Bestimmt eine ganze Menge, das solltest Du Microsoft fragen.
Nobbie
 
Posts: 13176
Joined: 09. March 2008 13:04

Re: Mysql lässt sich nicht mehr starten

Postby photogeist » 22. September 2023 06:48

Vielen Dank, das habe ich gefunden und werde das so ausprobieren. :-)
photogeist
 
Posts: 2
Joined: 21. September 2023 08:39
XAMPP version: 3.3.0
Operating System: Windows 11

Re: Mysql lässt sich nicht mehr starten

Postby Klaus_Schaefer » 10. December 2023 18:15

Cool - das hat bei mir das Problem jetzt auch gelöst!

Danke...!!!

Gruß
Klaus
Klaus_Schaefer
 
Posts: 3
Joined: 10. December 2023 15:20
XAMPP version: 8.2.12
Operating System: Windows Version: Home 64-bit

Re: Mysql lässt sich nicht mehr starten

Postby Szelegowitz » 31. December 2023 11:31

Hallo Leute,
mein MySql lässt sich nicht mehr starten. Hier ist der Log aus dem Shell:


Administrator@DESKTOP-9LJQ5TH c:\xampp
# mysqld --defaults-file=mysql\bin\my.ini --standalone --console
2023-12-31 11:28:41 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-12-31 11:28:41 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6252
2023-12-31 11:28:41 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-12-31 11:28:41 0 [Note] InnoDB: Uses event mutexes
2023-12-31 11:28:41 0 [Note] InnoDB: Compressed tables use zlib 1.3
2023-12-31 11:28:41 0 [Note] InnoDB: Number of pools: 1
2023-12-31 11:28:41 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-12-31 11:28:41 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-12-31 11:28:41 0 [Note] InnoDB: Completed initialization of buffer pool
2023-12-31 11:28:41 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-12-31 11:28:41 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-12-31 11:28:41 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-12-31 11:28:41 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-12-31 11:28:41 0 [Note] InnoDB: Waiting for purge to start
2023-12-31 11:28:42 0 [Note] InnoDB: 10.4.32 started; log sequence number 7646644; transaction id 1386
2023-12-31 11:28:42 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-12-31 11:28:42 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-12-31 11:28:42 0 [Note] Server socket created on IP: '::'.
2023-12-31 11:28:42 0 [ERROR] mysqld: Table '.\mysql\db' is marked as crashed and should be repaired
2023-12-31 11:28:42 0 [Note] InnoDB: Buffer pool(s) load completed at 231231 11:28:42
2023-12-31 11:28:42 0 [ERROR] mysqld: Index for table '.\mysql\db' is corrupt; try to repair it
2023-12-31 11:28:42 0 [ERROR] Couldn't repair table: mysql.db
2023-12-31 11:28:42 0 [ERROR] Fatal error: Can't open and lock privilege tables: Index for table 'db' is corrupt; try to repair it
2023-12-31 11:28:42 0 [ERROR] Aborting

Was kann ich tun?
Vielen Dank für jede Hilfe
Szelegowitz
 
Posts: 3
Joined: 28. December 2023 19:50
XAMPP version: 8.2.12
Operating System: Windows11


Return to XAMPP für Windows

Who is online

Users browsing this forum: No registered users and 82 guests