List:Community« Previous MessageNext Message »
From:Marco Cavazzini Date:February 4 2011 9:05am
Subject:MySQL community crash during dump
View as plain text  
Hello All,

I use MySQL 5.0.91-community-nt-log on Windows 2003 Web Edition with 
this character:

Intel Pentium 4 2,8 GHz
2 GB of RAM
32bit with PAE

MySQL server work it, but when launch a dump with "mysqldump" it crash.
It crash ever in different position of job, database and table. Seems 
I noted that MySQL use too RAM just before crash (normal use 100MB, 
first crash exceeds 400MB and system have about 1GB free).
After a crash we restart windows service and work it until next dump.

Attach configuration and log error:

110203 18:23:22 [Note] Crash recovery finished.
110203 18:23:23 [Note] D:\mysql-5\bin\mysqld-nt: ready for connections.
Version: '5.0.91-community-nt-log'  socket: ''  port: 3308  MySQL 
Community Edition (GPL)
110204  9:41:13 - mysqld got exception 0xc0000005 ;
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.
We will try our best to scrape up some info that will hopefully help 
the problem, but since we have already crashed, something is definitely 
and this may fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections 
= 237568 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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...
005900C4    mysqld-nt.exe!openfrm()[]
0050ED39    mysqld-nt.exe!open_unireg_entry()[]
005121FB    mysqld-nt.exe!open_table()[]
00513087    mysqld-nt.exe!open_tables()[]
0051362B    mysqld-nt.exe!open_normal_and_derived_tables()[]
00574714    mysqld-nt.exe!get_all_tables()[]
0056D060    mysqld-nt.exe!get_schema_tables_result()[]
00568D7F    mysqld-nt.exe!JOIN::exec()[]
00569F34    mysqld-nt.exe!mysql_select()[]
0056A37B    mysqld-nt.exe!handle_select()[]
0053BC12    mysqld-nt.exe!mysql_execute_command()[]
00542B11    mysqld-nt.exe!mysql_parse()[]
00543B0E    mysqld-nt.exe!dispatch_command()[]
00544E26    mysqld-nt.exe!do_command()[]
00545145    mysqld-nt.exe!handle_one_connection()[]
005F778B    mysqld-nt.exe!pthread_start()[my_winthread.c:85]
006E2A7F    mysqld-nt.exe!_threadstart()[thread.c:196]
77E6482F    kernel32.dll!GetModuleHandleA()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 18D58E40=show table status like '\_pagina'
The manual page at contains
information that should help you find out what is causing the crash.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!

# The MySQL server
tmpdir = d:/mysql-5/temp/
port        = 3308
basedir = d:/mysql-5/
datadir = d:/mysql-5/data/
key_buffer = 32M
max_allowed_packet = 4M
table_cache = 64
sort_buffer_size = 512k
read_buffer_size = 1M
read_rnd_buffer_size = 256K
myisam_sort_buffer_size = 8M
#thread_cache_size = 4
query_cache_size= 4M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 2

# 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!

# Disable Federated by default

# Replication Master Server (default)
# binary logging is required for replication

# 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 file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the file, unless you shutdown
#    the slave server, delete 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        = /tmp/
#log-update     = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 64M
#bdb_max_lock = 100000

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = D:\mysql-5\data/
innodb_data_file_path = ibdata1:50M:autoextend:max:50M
#innodb_log_group_home_dir = D:\mysql-5\data/
#innodb_log_arch_dir = D:\mysql-5\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 = 128M
innodb_additional_mem_pool_size = 16M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 16M
innodb_log_buffer_size = 32M
innodb_flush_log_at_trx_commit = 2
innodb_lock_wait_timeout = 50

Regards, Marco


MySQL community crash during dumpMarco Cavazzini4 Feb