MySql crashes every 3 minutes

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

MySql crashes every 3 minutes

Postby ThomasVit » 18. February 2019 11:43

Hi,

I have installed XAMPP for a colleague on a Windows server. ALl the services are running correctly except MySQL crashing every couple of minutes, the logs below FYI.
I am getting an error about mem size:

[ERROR] InnoDB: InnoDB: Unable to allocate memory of size 8056

But the mem size in the ini file is set to: 3072M

Here is my.ini file

# 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
# C:/xampp/mysql/bin/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is C:/xampp/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
[client]
# password = your_password
port = 3306
socket = "C:/xampp/mysql/mysql.sock"


# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port= 3306
socket = "C:/xampp/mysql/mysql.sock"
basedir = "C:/xampp/mysql"
tmpdir = "C:/xampp/tmp"
datadir = "C:/xampp/mysql/data"
pid_file = "mysql.pid"
# enable-named-pipe
key_buffer = 512M
max_allowed_packet = 10M
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
log_error = "mysql_error.log"

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

# Where do all the plugins live
plugin_dir = "C:/xampp/mysql/lib/plugin/"

# 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
#skip-networking
#skip-federated

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

# 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:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# 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:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# 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
#log-bin=mysql-bin


# Point the following paths to different dedicated disks
#tmpdir = "C:/xampp/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
#skip-innodb
innodb_data_home_dir = "C:/xampp/mysql/data"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "C:/xampp/mysql/data"
#innodb_log_arch_dir = "C:/xampp/mysql/data"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 3072M
innodb_additional_mem_pool_size = 20M
## Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 256M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

## UTF 8 Settings
#init-connect=\'SET NAMES utf8\'
#collation_server=utf8_unicode_ci
#character_set_server=utf8
#skip-character-set-client-handshake
#character_sets-dir="C:/xampp/mysql/share/charsets"

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout



Logs:

2019-02-18 11:34:21 1b6c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2019-02-18 11:34:21 7020 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-02-18 11:34:21 7020 [Note] InnoDB: The InnoDB memory heap is disabled
2019-02-18 11:34:21 7020 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-02-18 11:34:21 7020 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-02-18 11:34:21 7020 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-02-18 11:34:21 7020 [Note] InnoDB: Using generic crc32 instructions
2019-02-18 11:34:21 7020 [Note] InnoDB: Initializing buffer pool, size = 3.0G
2019-02-18 11:34:21 7020 [Note] InnoDB: Completed initialization of buffer pool
2019-02-18 11:34:21 7020 [Note] InnoDB: Highest supported file format is Barracuda.
2019-02-18 11:34:21 7020 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence number 11980734326 in the ib_logfiles!
2019-02-18 11:34:24 7020 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-02-18 11:34:25 7020 [Note] InnoDB: 128 rollback segment(s) are active.
2019-02-18 11:34:25 7020 [Note] InnoDB: Waiting for purge to start
2019-02-18 11:34:25 7020 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 11980734326
2019-02-18 11:34:25 7268 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-02-18 11:34:25 7020 [Note] Plugin 'FEEDBACK' is disabled.
2019-02-18 11:34:25 7020 [Note] Server socket created on IP: '::'.
2019-02-18 11:34:25 7020 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.37-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2019-02-18 11:35:01 5084 [ERROR] InnoDB: InnoDB: Unable to allocate memory of size 8056.

2019-02-18 11:35:01 13dc InnoDB: Assertion failure in thread 5084 in file ha_innodb.cc line 22057
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
190218 11:35:01 [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.1.37-MariaDB
key_buffer_size=536870912
read_buffer_size=262144
max_used_connections=2
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1295040 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2019-02-18 11:36:09 1900 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2019-02-18 11:36:09 6400 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-02-18 11:36:09 6400 [Note] InnoDB: The InnoDB memory heap is disabled
2019-02-18 11:36:09 6400 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-02-18 11:36:09 6400 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-02-18 11:36:09 6400 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-02-18 11:36:09 6400 [Note] InnoDB: Using generic crc32 instructions
2019-02-18 11:36:09 6400 [Note] InnoDB: Initializing buffer pool, size = 3.0G
2019-02-18 11:36:09 6400 [Note] InnoDB: Completed initialization of buffer pool
2019-02-18 11:36:09 6400 [Note] InnoDB: Highest supported file format is Barracuda.
2019-02-18 11:36:09 6400 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence number 11980734558 in the ib_logfiles!
2019-02-18 11:36:12 6400 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-02-18 11:36:14 6400 [Note] InnoDB: 128 rollback segment(s) are active.
2019-02-18 11:36:14 6400 [Note] InnoDB: Waiting for purge to start
2019-02-18 11:36:14 6400 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 11980734558
2019-02-18 11:36:14 6944 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-02-18 11:36:14 6400 [Note] Plugin 'FEEDBACK' is disabled.
2019-02-18 11:36:14 6400 [Note] Server socket created on IP: '::'.
2019-02-18 11:36:14 6400 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.37-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2019-02-18 11:36:49 7312 [ERROR] InnoDB: InnoDB: Unable to allocate memory of size 8056.

2019-02-18 11:36:49 1c90 InnoDB: Assertion failure in thread 7312 in file ha_innodb.cc line 22057
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
190218 11:36:49 [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.1.37-MariaDB
key_buffer_size=536870912
read_buffer_size=262144
max_used_connections=2
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1295040 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
ThomasVit
 
Posts: 1
Joined: 18. February 2019 11:35
XAMPP version: 7.3.1
Operating System: Windows Server 2019 x64

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 42 guests