Local XAMPP Mysql stop starting correctly

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Local XAMPP Mysql stop starting correctly

Postby Tortliena » 04. February 2020 16:07

Hi there!

Since, well... today, my local installation of XAMPP along with Mediawiki is not doing so well. More specifically, I cannot start MySQL/mariaDB anymore, although I didn't change none of the configuration files or general XAMPP status. Only thing that changed directly related to Mysql is some new pages/modifications on my wiki (so some table changes).

Here are the details of my setup :
ApacheFriends XAMPP Version 7.4.1 (Windows 10)
+ Apache 2.4.41
+ MariaDB 10.4.11
+ PHP 7.4.1 (VC15 X86 64bit thread safe) + PEAR
+ phpMyAdmin 4.9.2
+ OpenSSL 1.1.0g
+ ADOdb 518a
+ Mercury Mail Transport System v4.63 (not included in the portable version)
+ FileZilla FTP Server 0.9.41 (not included in the portable version)
+ Webalizer 2.23-04 (not included in the portable version)
+ Strawberry Perl Portable
+ Tomcat 7.0.99
+ XAMPP Control Panel Version 3.2.4.
+ XAMPP mailToDisk 1.0 (write emails via PHP on local disk in <xampp>\mailoutput. Activated in the php.ini as mail default.)

Only Apache and MySQL are launched on computer startup (the others aren't necessary for mediawiki as far as I remember).
The mediawiki installation has been made manually, without the Bitnami thingy, and according to this page : https://www.mediawiki.org/wiki/Manual:Installing_MediaWiki_on_XAMPP

You can find here my my.ini. Shouldn't have changed from the original one at installation, but just in case :

Code: Select all
# Example MySQL config file for small systems.
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't use much resources.
# You can copy this file to
# D:/Serveurs/XAMPPdoc/mysql/bin/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is D:/Serveurs/XAMPPdoc/mysql/data) or
# ~/.my.cnf to set user-specific options.
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
# password       = your_password

# Here follows entries for some specific programs

# The MySQL server
# enable-named-pipe

# Change here for bind listening
# bind-address=""
# bind-address = ::1          # for ipv6

# Where do all the plugins live

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# commented in by lampp security

# Replication Master Server (default)
# binary logging is required for replication
# log-bin deactivated by default since XAMPP 1.4.11

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id   =1

# Replication Slave (comment out master section to use this)
# To configure this host as a replication slave, you can choose between
# two methods :
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#    Example:
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
# OR
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
# The replication master for this slave - required
#master-host     =   <hostname>
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
# binary logging - not required for slaves, but recommended

# Point the following paths to different dedicated disks
#tmpdir = "D:/Serveurs/XAMPPdoc/tmp"
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Comment the following if you are using InnoDB tables
#innodb_log_arch_dir = "D:/Serveurs/XAMPPdoc/mysql/data"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
## Set .._log_file_size to 25 % of buffer pool size

## UTF 8 Settings
#init-connect=\'SET NAMES utf8\'


# Remove the next comment character if you are not familiar with SQL




Here are the logs on mysql_error.log; Apart from the last line which seems strange (the ip?), there is no specific error :/ :

Code: Select all
InnoDB: using atomic writes.
2020-02-04 14:41:18 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-02-04 14:41:18 0 [Note] InnoDB: Uses event mutexes
2020-02-04 14:41:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-02-04 14:41:18 0 [Note] InnoDB: Number of pools: 1
2020-02-04 14:41:18 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-02-04 14:41:18 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2020-02-04 14:41:18 0 [Note] InnoDB: Completed initialization of buffer pool
2020-02-04 14:41:20 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-02-04 14:41:20 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-02-04 14:41:20 0 [Note] InnoDB: Setting file 'D:\Serveurs\XAMPPdoc\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-02-04 14:41:20 0 [Note] InnoDB: File 'D:\Serveurs\XAMPPdoc\mysql\data\ibtmp1' size is now 12 MB.
2020-02-04 14:41:20 0 [Note] InnoDB: 10.4.11 started; log sequence number 35854436; transaction id 32938
2020-02-04 14:41:20 0 [Note] InnoDB: Loading buffer pool(s) from D:\Serveurs\XAMPPdoc\mysql\data\ib_buffer_pool
2020-02-04 14:41:20 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-02-04 14:41:20 0 [Note] Server socket created on IP: '::'.

I also tried a manual start with mysql_start.bat, without success :
Code: Select all
Diese Eingabeforderung nicht waehrend des Running beenden
Please dont close Window while MySQL is running
MySQL is trying to start
Please wait  ...
MySQL is starting with mysql\bin\my.ini (console)
2020-02-04 15:06:19 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.
2020-02-04 15:06:19 0 [Note] mysql\bin\mysqld (mysqld 10.4.11-MariaDB) starting as process 7872 ...

MySQL konnte nicht gestartet werden
MySQL could not be started

So here are a few things I already tried :

  • Clean Temporary files, restart computer (maybe with some good fortune cookies :p?)
  • Manual Mysql start with .bat (administrator mode)
  • Changing Mysql port to two random values (14525 and 8412) and retry.

Given the specific situation, it seems unlikely that I get a solution. However, I'd like to avoid losing my wiki pages since the last two weeks (the date of my last backup), so is there at least a way to create a save of the databases without having Mysql on? I honestly never thought that things would go awry this soon, and without doing anything peculiar!

P.S.: By the way, the help page on the control panel doesn't link to the correct page apparently ;p.
Posts: 2
Joined: 04. February 2020 14:48
XAMPP version: 7.4.1
Operating System: Windows

SOLVED : Local XAMPP Mysql stop starting correctly

Postby Tortliena » 06. February 2020 15:31

The issue has been sorted out. Sort of. In fact, I am still unaware of the original cause of MySQL crash, though if it is probably linked to database corruption. However, I still managed to recover most if not all lost data by searching manually the database files with a text editor. It ain't clearly the best trick, but since there wasn't much changes in two weeks and I don't care much about users data nor revision changes on pages, this seemed the most straightforward thing to do. After all, the most important thing is the content of the pages!

Since I still don't know what is the exact cause, I guess I will need to do weekly backups (instead of monthly ones) in order to limit damage if it happens again. Oh well!
Posts: 2
Joined: 04. February 2020 14:48
XAMPP version: 7.4.1
Operating System: Windows

Re: Local XAMPP Mysql stop starting correctly

Postby il_dottore » 08. February 2020 10:48

Try to install XAMPP 7.3.12 for me its working
Posts: 10
Joined: 09. October 2019 18:13
XAMPP version: 7.3.12
Operating System: Windows 10 64 bit

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 53 guests