I was testing an apparent performance issue while I got a strange perl
message , claiming it (with perl/DBI)
DBD driver has not implemented the AutoCommit attribute at perlscript.pl line 1064, <IN> line 12911.
Issuing rollback() for database handle being DESTROY'd without explicit disconnect(), <IN> line 12911
this was strange, since I tested it on a test program and AutoCommit worked fine.
Anyway, the code died, I did some changes and it worked ok, until it hit the same message. The problem now is that (I rebooted the server) I can do
/usr/bin/mysqld_safe fine, but when I do
mysql -u user -ppasswd database
it just hangs there(and this is also the case when I try to connect via DBI)
I am using 4.0.1 with InnoDB. Could it be that I ran out of table space?
/var/lib/mysql/linux.err complains that:
/usr/sbin/mysqld: ready for connections
InnoDB: Warning: operating system error number 4 in a file
operation.
InnoDB: Cannot continue operation.
Number of processes running now: 0
020818 21:56:29 mysqld restarted
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 43 1452255266
InnoDB: Doing recovery: scanned up to log sequence number
43 1452320768
InnoDB: Doing recovery: scanned up to log sequence number
43 1452386304
.....
What should I do now?
Here is /etc/my.cnf
# Example mysql config file for very large systems.
#
# This is for large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/mf.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /var/lib/mysql) or
# ~/.my.cnf to set user-specific options.
#
# One can in this file use all long options that the program supports.
# If you want to know which options a program support, run the program
# with --help option.
# The following options will be passed to all MySQL clients
[client]
#password = your_password
port = 3306
socket = /var/lib/mysql/mysql.sock
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
set-variable = key_buffer_size=500M
set-variable = key_buffer=100M
set-variable = max_allowed_packet=1M
set-variable = table_cache=512
set-variable = max_connections=10
set-variable = tmp_table_size=400M
set-variable = sort_buffer=2M
set-variable = record_buffer=2M
set-variable = thread_cache=8
set-variable = thread_concurrency=4 # Try number of
CPU's*2
#set-variable = myisam_sort_buffer_size=64M
set-variable = myisam_sort_buffer_size=4M
innodb_data_home_dir=
#and then use absolute file paths
#innodb_data_file_path=ibdata1:2000M;ibdata2:2000M;ibdata3:2
000M;ibdata4:2000M;ibdata5:2000M;ibdata6:2000M;ibdata7:2000M
;ibdata8:2000M
innodb_data_file_path=/var/lib/mysql/ibdata1:2000M;/var/lib/
mysql/ibdata2:2000M;/var/lib/mysql/ibdata3:2000M;/var/lib/my
sql/ibdata4:2000M;/var/lib/mysql/ibdata5:2000M;/var/lib/mysq
l/ibdata6:2000M;/var/lib/mysql/ibdata7:2000M;/var/lib/mysql/
ibdata8:2000M;/usr/ibdata/ibdata9:2000M;/usr/ibdata/ibdata10
:2000M;/usr/ibdata/ibdata11:2000M;/usr/ibdata/ibdata12:2000M
;/ibdata/ibdata13:2000M;/ibdata/ibdata14:2000M;/ibdata/ibdat
a15:2000M;/var/lib/mysql/ibdata16:2000M;/var/lib/mysql/ibdat
a17:2000M;/var/lib/mysql/ibdata18:2000M;/var/lib/mysql/ibdat
a19:2000M;/var/lib/mysql/ibdata20:2000M;/var/lib/mysql/ibdat
a21:2000M
#;/usr/ibdata/ibdata9:2000M;/usr/ibdata/ibdata10:2000M
## Comment next line if you do not need recovery(the
hostname-bin.xxx files)
#log-bin
##
server-id = 1
#set-variable = open-files-limit=8192 #ulimit is
1024,hard 8192
set-variable = innodb_buffer_pool_size=1100M
# so that innodb_buffer_pool
size+key_buffer+max_connections*
(sort_buffer+record_buffer+2M)=1100+100+10*(2+2+2)
=1260<2000M=RAM
set-variable = innodb_additional_mem_pool_size=700M
set-variable = innodb_log_file_size=1000M
set-variable = innodb_log_buffer_size=20M
# helps for large transactions
# Uncomment the following if you are using BDB tables
#set-variable = bdb_cache_size=384M
#set-variable = bdb_max_lock=100000
# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname
[mysqldump]
quick
set-variable = max_allowed_packet=256M
[mysql]
no-auto-rehash
#safe-updates # Remove the comment character if you are not familiar with SQL
[isamchk]
set-variable = key_buffer=256M
set-variable = sort_buffer=256M
set-variable = read_buffer=2M
set-variable = write_buffer=2M
[myisamchk]
#set-variable = key_buffer=256M
#set-variable = sort_buffer=256M
#set-variable = read_buffer=2M
#set-variable = write_buffer=2M
set-variable = key_buffer=25M
set-variable = sort_buffer=25M
set-variable = read_buffer=2M
set-variable = write_buffer=2M
[mysqlhotcopy]
interactive-timeout
-----------------------
below is the full copy of /var/lib/mysql/linux.err:
020418 21:50:46 mysqld started
InnoDB: Data file /ibdata/ibdata13 did not exist: new to be
created
InnoDB: Setting file /ibdata/ibdata13 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /ibdata/ibdata14 did not exist: new to be
created
InnoDB: Setting file /ibdata/ibdata14 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /ibdata/ibdata15 did not exist: new to be
created
InnoDB: Setting file /ibdata/ibdata15 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 3 2932307830
020418 21:56:38 InnoDB: Started/usr/sbin/mysqld: ready for
connections
Number of processes running now: 1
mysqld process hanging, pid 1081 - killed
020419 14:37:39 mysqld restarted
020419 14:37:39 Can't start server: Bind on TCP/IP port: Address already in use
020419 14:37:39 Do you already have another mysqld server running on port: 3306 ?
020419 14:37:39 Aborting
020419 14:37:39 /usr/sbin/mysqld: Shutdown Complete
020419 14:37:39 mysqld ended
020419 14:40:23 mysqld started
InnoDB: Data file /var/lib/mysql/ibdata16 did not exist: new to be created
InnoDB: Setting file /var/lib/mysql/ibdata16 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /var/lib/mysql/ibdata17 did not exist:
new to be created
InnoDB: Setting file /var/lib/mysql/ibdata17 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
mysqld got signal 11;
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 diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=402649088
record_buffer=2093056
sort_buffer=2097144
max_used_connections=0
max_connections=10
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 434131 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...
Bogus stack limit or frame pointer, fp=0xbfffb8a8, stack_bottom=0x64, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x20 is invalid pointer
thd->thread_id=0
Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 0 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid.
The manual page at contains
information that should help you find out what is causing the crash.
020419 14:44:28 mysqld ended
020419 14:45:04 mysqld started
InnoDB: Error: data file /var/lib/mysql/ibdata17 is of
different size
InnoDB: than specified in the .cnf file!
InnoDB: Could not open data files
020419 14:45:07 Can't init databases
020419 14:45:07 mysqld ended
020419 14:46:37 mysqld started
InnoDB: Data file /var/lib/mysql/ibdata17 did not exist:
new to be created
InnoDB: Setting file /var/lib/mysql/ibdata17 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /var/lib/mysql/ibdata18 did not exist:
new to be created
InnoDB: Setting file /var/lib/mysql/ibdata18 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /var/lib/mysql/ibdata19 did not exist:
new to be created
InnoDB: Setting file /var/lib/mysql/ibdata19 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /var/lib/mysql/ibdata20 did not exist:
new to be created
InnoDB: Setting file /var/lib/mysql/ibdata20 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 4 2930252660
020419 14:55:22 InnoDB: Started
/usr/sbin/mysqld: ready for connections
020419 15:39:25 /usr/sbin/mysqld: Normal shutdown
020419 15:39:26 /usr/sbin/mysqld: Forcing close of thread 42 user:
020709 22:36:25 mysqld started
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 24 3493955977
020709 22:36:34 InnoDB: Started
/usr/sbin/mysqld: ready for connections
mysqld got signal 11;
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 diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=104853504
record_buffer=2093056
sort_buffer=2097144
max_used_connections=4
max_connections=10
threads_connected=-1
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 143315 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
You seem to be running 32-bit Linux and have -1 concurrent connections.
If you have not changed STACK_SIZE in LinuxThreads and built the binary
yourself, LinuxThreads is quite likely to steal a part of the global heap for
the thread stack. Please read
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...
Bogus stack limit or frame pointer, fp=0xbfe1f4e8, stack_bottom=0xbfe7fcb8, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
InnoDB: Assertion failure in thread 53262 in file trx0trx.c
line 228
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
Number of processes running now: 1
mysqld process hanging, pid 1006 - killed
020724 21:29:04 mysqld restarted
020724 21:29:04 Can't start server: Bind on TCP/IP port: Address already in use
020724 21:29:04 Do you already have another mysqld server running on port: 3306 ?
020724 21:29:04 Aborting
020724 21:29:04 /usr/sbin/mysqld: Shutdown Complete
020724 21:29:04 mysqld ended
020724 21:32:42 mysqld started
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 31 4095432576
020724 21:32:49 InnoDB: Started
/usr/sbin/mysqld: ready for connections
020731 18:08:23 /usr/sbin/mysqld: Normal shutdown
020731 18:08:24 InnoDB: Starting shutdown...
020731 18:15:02 mysqld started
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 32 1574840608
020731 18:15:09 InnoDB: Started
/usr/sbin/mysqld: ready for connections
020731 19:47:45 /usr/sbin/mysqld: Normal shutdown
020731 19:47:45 InnoDB: Starting shutdown...
020731 22:43:18 mysqld started
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 32 1574840618
020731 22:43:26 InnoDB: Started
/usr/sbin/mysqld: ready for connections
Status information:
Current dir: /var/lib/mysql/
Current locks:
key_cache status:
blocks used: 10
not flushed: 0
w_requests: 0
writes: 0
r_requests: 0
reads: 0
handler status:
read_key: 0
read_next: 0
read_rnd 0
read_first: 0
write: 0
delete 0
update: 0
Table status:
Opened tables: 0
Open tables: 0
Open files: 0
Open streams: 0
Number of processes running now: 0
020816 23:01:00 mysqld restarted
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 43 1440784804
InnoDB: Doing recovery: scanned up to log sequence number
43 1440849920
InnoDB: Doing recovery: scanned up to log sequence number
43 1440915456
InnoDB: Doing recovery: scanned up to log sequence number
43 1440980992
InnoDB: Doing recovery: scanned up to log sequence number
43 1441046528
InnoDB: Doing recovery: scanned up to log sequence number
43 1441112064
InnoDB: Doing recovery: scanned up to log sequence number
43 1441177600
InnoDB: Doing recovery: scanned up to log sequence number
43 1441243136
InnoDB: Doing recovery: scanned up to log sequence number
43 1441308672
InnoDB: Doing recovery: scanned up to log sequence number
43 1441374208
InnoDB: Doing recovery: scanned up to log sequence number
43 1441439744
InnoDB: After this prints a line for every 10th scan sweep:
InnoDB: Doing recovery: scanned up to log sequence number
43 1442095104
InnoDB: Doing recovery: scanned up to log sequence number
43 1442750464
InnoDB: Doing recovery: scanned up to log sequence number
43 1443405824
InnoDB: Doing recovery: scanned up to log sequence number
43 1444061184
InnoDB: Doing recovery: scanned up to log sequence number
43 1444716544
InnoDB: Doing recovery: scanned up to log sequence number
43 1445371904
InnoDB: Doing recovery: scanned up to log sequence number
43 1446027264
InnoDB: Doing recovery: scanned up to log sequence number
43 1446682624
InnoDB: Doing recovery: scanned up to log sequence number
43 1447337984
InnoDB: Doing recovery: scanned up to log sequence number
43 1447993344
InnoDB: Doing recovery: scanned up to log sequence number
43 1448648704
InnoDB: Doing recovery: scanned up to log sequence number
43 1449304064
InnoDB: Doing recovery: scanned up to log sequence number
43 1449959424
InnoDB: Doing recovery: scanned up to log sequence number
43 1450614784
InnoDB: Starting an apply batch of log records to the
database...
InnoDB: Apply batch completed
020816 23:08:21 InnoDB: Started
/usr/sbin/mysqld: ready for connections
InnoDB: Warning: operating system error number 4 in a file
operation.
InnoDB: Cannot continue operation.
Number of processes running now: 0
020818 21:56:29 mysqld restarted
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 43 1452255266
InnoDB: Doing recovery: scanned up to log sequence number
43 1452320768
I........
InnoDB: Doing recovery: scanned up to log sequence number
43 1452845056
InnoDB: Doing recovery: scanned up to log sequence number
43 1452910592
InnoDB: After this prints a line for every 10th scan sweep:
........
overy: scanned up to log sequence number 43 1477158912
I
message , claiming it (with perl/DBI)
DBD driver has not implemented the AutoCommit attribute at perlscript.pl line 1064, <IN> line 12911.
Issuing rollback() for database handle being DESTROY'd without explicit disconnect(), <IN> line 12911
this was strange, since I tested it on a test program and AutoCommit worked fine.
Anyway, the code died, I did some changes and it worked ok, until it hit the same message. The problem now is that (I rebooted the server) I can do
/usr/bin/mysqld_safe fine, but when I do
mysql -u user -ppasswd database
it just hangs there(and this is also the case when I try to connect via DBI)
I am using 4.0.1 with InnoDB. Could it be that I ran out of table space?
/var/lib/mysql/linux.err complains that:
/usr/sbin/mysqld: ready for connections
InnoDB: Warning: operating system error number 4 in a file
operation.
InnoDB: Cannot continue operation.
Number of processes running now: 0
020818 21:56:29 mysqld restarted
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 43 1452255266
InnoDB: Doing recovery: scanned up to log sequence number
43 1452320768
InnoDB: Doing recovery: scanned up to log sequence number
43 1452386304
.....
What should I do now?
Here is /etc/my.cnf
# Example mysql config file for very large systems.
#
# This is for large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/mf.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /var/lib/mysql) or
# ~/.my.cnf to set user-specific options.
#
# One can in this file use all long options that the program supports.
# If you want to know which options a program support, run the program
# with --help option.
# The following options will be passed to all MySQL clients
[client]
#password = your_password
port = 3306
socket = /var/lib/mysql/mysql.sock
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
set-variable = key_buffer_size=500M
set-variable = key_buffer=100M
set-variable = max_allowed_packet=1M
set-variable = table_cache=512
set-variable = max_connections=10
set-variable = tmp_table_size=400M
set-variable = sort_buffer=2M
set-variable = record_buffer=2M
set-variable = thread_cache=8
set-variable = thread_concurrency=4 # Try number of
CPU's*2
#set-variable = myisam_sort_buffer_size=64M
set-variable = myisam_sort_buffer_size=4M
innodb_data_home_dir=
#and then use absolute file paths
#innodb_data_file_path=ibdata1:2000M;ibdata2:2000M;ibdata3:2
000M;ibdata4:2000M;ibdata5:2000M;ibdata6:2000M;ibdata7:2000M
;ibdata8:2000M
innodb_data_file_path=/var/lib/mysql/ibdata1:2000M;/var/lib/
mysql/ibdata2:2000M;/var/lib/mysql/ibdata3:2000M;/var/lib/my
sql/ibdata4:2000M;/var/lib/mysql/ibdata5:2000M;/var/lib/mysq
l/ibdata6:2000M;/var/lib/mysql/ibdata7:2000M;/var/lib/mysql/
ibdata8:2000M;/usr/ibdata/ibdata9:2000M;/usr/ibdata/ibdata10
:2000M;/usr/ibdata/ibdata11:2000M;/usr/ibdata/ibdata12:2000M
;/ibdata/ibdata13:2000M;/ibdata/ibdata14:2000M;/ibdata/ibdat
a15:2000M;/var/lib/mysql/ibdata16:2000M;/var/lib/mysql/ibdat
a17:2000M;/var/lib/mysql/ibdata18:2000M;/var/lib/mysql/ibdat
a19:2000M;/var/lib/mysql/ibdata20:2000M;/var/lib/mysql/ibdat
a21:2000M
#;/usr/ibdata/ibdata9:2000M;/usr/ibdata/ibdata10:2000M
## Comment next line if you do not need recovery(the
hostname-bin.xxx files)
#log-bin
##
server-id = 1
#set-variable = open-files-limit=8192 #ulimit is
1024,hard 8192
set-variable = innodb_buffer_pool_size=1100M
# so that innodb_buffer_pool
size+key_buffer+max_connections*
(sort_buffer+record_buffer+2M)=1100+100+10*(2+2+2)
=1260<2000M=RAM
set-variable = innodb_additional_mem_pool_size=700M
set-variable = innodb_log_file_size=1000M
set-variable = innodb_log_buffer_size=20M
# helps for large transactions
# Uncomment the following if you are using BDB tables
#set-variable = bdb_cache_size=384M
#set-variable = bdb_max_lock=100000
# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname
[mysqldump]
quick
set-variable = max_allowed_packet=256M
[mysql]
no-auto-rehash
#safe-updates # Remove the comment character if you are not familiar with SQL
[isamchk]
set-variable = key_buffer=256M
set-variable = sort_buffer=256M
set-variable = read_buffer=2M
set-variable = write_buffer=2M
[myisamchk]
#set-variable = key_buffer=256M
#set-variable = sort_buffer=256M
#set-variable = read_buffer=2M
#set-variable = write_buffer=2M
set-variable = key_buffer=25M
set-variable = sort_buffer=25M
set-variable = read_buffer=2M
set-variable = write_buffer=2M
[mysqlhotcopy]
interactive-timeout
-----------------------
below is the full copy of /var/lib/mysql/linux.err:
020418 21:50:46 mysqld started
InnoDB: Data file /ibdata/ibdata13 did not exist: new to be
created
InnoDB: Setting file /ibdata/ibdata13 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /ibdata/ibdata14 did not exist: new to be
created
InnoDB: Setting file /ibdata/ibdata14 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /ibdata/ibdata15 did not exist: new to be
created
InnoDB: Setting file /ibdata/ibdata15 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 3 2932307830
020418 21:56:38 InnoDB: Started/usr/sbin/mysqld: ready for
connections
Number of processes running now: 1
mysqld process hanging, pid 1081 - killed
020419 14:37:39 mysqld restarted
020419 14:37:39 Can't start server: Bind on TCP/IP port: Address already in use
020419 14:37:39 Do you already have another mysqld server running on port: 3306 ?
020419 14:37:39 Aborting
020419 14:37:39 /usr/sbin/mysqld: Shutdown Complete
020419 14:37:39 mysqld ended
020419 14:40:23 mysqld started
InnoDB: Data file /var/lib/mysql/ibdata16 did not exist: new to be created
InnoDB: Setting file /var/lib/mysql/ibdata16 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /var/lib/mysql/ibdata17 did not exist:
new to be created
InnoDB: Setting file /var/lib/mysql/ibdata17 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
mysqld got signal 11;
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 diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=402649088
record_buffer=2093056
sort_buffer=2097144
max_used_connections=0
max_connections=10
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 434131 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...
Bogus stack limit or frame pointer, fp=0xbfffb8a8, stack_bottom=0x64, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x20 is invalid pointer
thd->thread_id=0
Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 0 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid.
The manual page at contains
information that should help you find out what is causing the crash.
020419 14:44:28 mysqld ended
020419 14:45:04 mysqld started
InnoDB: Error: data file /var/lib/mysql/ibdata17 is of
different size
InnoDB: than specified in the .cnf file!
InnoDB: Could not open data files
020419 14:45:07 Can't init databases
020419 14:45:07 mysqld ended
020419 14:46:37 mysqld started
InnoDB: Data file /var/lib/mysql/ibdata17 did not exist:
new to be created
InnoDB: Setting file /var/lib/mysql/ibdata17 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /var/lib/mysql/ibdata18 did not exist:
new to be created
InnoDB: Setting file /var/lib/mysql/ibdata18 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /var/lib/mysql/ibdata19 did not exist:
new to be created
InnoDB: Setting file /var/lib/mysql/ibdata19 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Data file /var/lib/mysql/ibdata20 did not exist:
new to be created
InnoDB: Setting file /var/lib/mysql/ibdata20 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 4 2930252660
020419 14:55:22 InnoDB: Started
/usr/sbin/mysqld: ready for connections
020419 15:39:25 /usr/sbin/mysqld: Normal shutdown
020419 15:39:26 /usr/sbin/mysqld: Forcing close of thread 42 user:
020709 22:36:25 mysqld started
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 24 3493955977
020709 22:36:34 InnoDB: Started
/usr/sbin/mysqld: ready for connections
mysqld got signal 11;
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 diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=104853504
record_buffer=2093056
sort_buffer=2097144
max_used_connections=4
max_connections=10
threads_connected=-1
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 143315 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
You seem to be running 32-bit Linux and have -1 concurrent connections.
If you have not changed STACK_SIZE in LinuxThreads and built the binary
yourself, LinuxThreads is quite likely to steal a part of the global heap for
the thread stack. Please read
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...
Bogus stack limit or frame pointer, fp=0xbfe1f4e8, stack_bottom=0xbfe7fcb8, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
InnoDB: Assertion failure in thread 53262 in file trx0trx.c
line 228
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
Number of processes running now: 1
mysqld process hanging, pid 1006 - killed
020724 21:29:04 mysqld restarted
020724 21:29:04 Can't start server: Bind on TCP/IP port: Address already in use
020724 21:29:04 Do you already have another mysqld server running on port: 3306 ?
020724 21:29:04 Aborting
020724 21:29:04 /usr/sbin/mysqld: Shutdown Complete
020724 21:29:04 mysqld ended
020724 21:32:42 mysqld started
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 31 4095432576
020724 21:32:49 InnoDB: Started
/usr/sbin/mysqld: ready for connections
020731 18:08:23 /usr/sbin/mysqld: Normal shutdown
020731 18:08:24 InnoDB: Starting shutdown...
020731 18:15:02 mysqld started
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 32 1574840608
020731 18:15:09 InnoDB: Started
/usr/sbin/mysqld: ready for connections
020731 19:47:45 /usr/sbin/mysqld: Normal shutdown
020731 19:47:45 InnoDB: Starting shutdown...
020731 22:43:18 mysqld started
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 32 1574840618
020731 22:43:26 InnoDB: Started
/usr/sbin/mysqld: ready for connections
Status information:
Current dir: /var/lib/mysql/
Current locks:
key_cache status:
blocks used: 10
not flushed: 0
w_requests: 0
writes: 0
r_requests: 0
reads: 0
handler status:
read_key: 0
read_next: 0
read_rnd 0
read_first: 0
write: 0
delete 0
update: 0
Table status:
Opened tables: 0
Open tables: 0
Open files: 0
Open streams: 0
Number of processes running now: 0
020816 23:01:00 mysqld restarted
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 43 1440784804
InnoDB: Doing recovery: scanned up to log sequence number
43 1440849920
InnoDB: Doing recovery: scanned up to log sequence number
43 1440915456
InnoDB: Doing recovery: scanned up to log sequence number
43 1440980992
InnoDB: Doing recovery: scanned up to log sequence number
43 1441046528
InnoDB: Doing recovery: scanned up to log sequence number
43 1441112064
InnoDB: Doing recovery: scanned up to log sequence number
43 1441177600
InnoDB: Doing recovery: scanned up to log sequence number
43 1441243136
InnoDB: Doing recovery: scanned up to log sequence number
43 1441308672
InnoDB: Doing recovery: scanned up to log sequence number
43 1441374208
InnoDB: Doing recovery: scanned up to log sequence number
43 1441439744
InnoDB: After this prints a line for every 10th scan sweep:
InnoDB: Doing recovery: scanned up to log sequence number
43 1442095104
InnoDB: Doing recovery: scanned up to log sequence number
43 1442750464
InnoDB: Doing recovery: scanned up to log sequence number
43 1443405824
InnoDB: Doing recovery: scanned up to log sequence number
43 1444061184
InnoDB: Doing recovery: scanned up to log sequence number
43 1444716544
InnoDB: Doing recovery: scanned up to log sequence number
43 1445371904
InnoDB: Doing recovery: scanned up to log sequence number
43 1446027264
InnoDB: Doing recovery: scanned up to log sequence number
43 1446682624
InnoDB: Doing recovery: scanned up to log sequence number
43 1447337984
InnoDB: Doing recovery: scanned up to log sequence number
43 1447993344
InnoDB: Doing recovery: scanned up to log sequence number
43 1448648704
InnoDB: Doing recovery: scanned up to log sequence number
43 1449304064
InnoDB: Doing recovery: scanned up to log sequence number
43 1449959424
InnoDB: Doing recovery: scanned up to log sequence number
43 1450614784
InnoDB: Starting an apply batch of log records to the
database...
InnoDB: Apply batch completed
020816 23:08:21 InnoDB: Started
/usr/sbin/mysqld: ready for connections
InnoDB: Warning: operating system error number 4 in a file
operation.
InnoDB: Cannot continue operation.
Number of processes running now: 0
020818 21:56:29 mysqld restarted
InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 43 1452255266
InnoDB: Doing recovery: scanned up to log sequence number
43 1452320768
I........
InnoDB: Doing recovery: scanned up to log sequence number
43 1452845056
InnoDB: Doing recovery: scanned up to log sequence number
43 1452910592
InnoDB: After this prints a line for every 10th scan sweep:
........
overy: scanned up to log sequence number 43 1477158912
I