List:General Discussion« Previous MessageNext Message »
From:BAUMEISTER Alexandre Date:March 19 2002 9:50am
Subject:InnoDB: Assertion failure in thread 10 in file btr0btr.c line 574
View as plain text  
Bonjour,

  We  have  Mysql  continually crashing with this assertion failure in
  InnoDB.

  Mysql-3.23.49 configured with by :
============================================================================
  ./configure         --prefix=/usr/local/mysql        --without-bench
  --enable-thread-safe-client       --with-innodb      --without-debug
  --without-berkeley-db --without-raid --enable-local-infile
============================================================================

  Here are the logs :
============================================================================
020319 10:43:13  mysqld restarted
020319 10:43:16  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 0 722513183
InnoDB: Doing recovery: scanned up to log sequence number 0 722514672
020319 10:43:16  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
020319 10:43:18  InnoDB: Flushing modified pages from the buffer pool...
020319 10:43:18  InnoDB: Started
/usr/local/mysql/libexec/mysqld: ready for connections
020319 10:43:18  Warning: Checking table:   './popup/campagne'
020319 10:43:24  Warning: Checking table:   './boursoscan/abonnes'
InnoDB: Assertion failure in thread 10 in file btr0btr.c line 574
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@stripped
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 agaist 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=134213632
record_buffer=1044480
sort_buffer=2097144
max_used_connections=82
max_connections=650
threads_connected=32
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 2125262 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation
============================================================================


  And here are the config options :
============================================================================
[mysqld]
port            = 3306
socket          = /tmp/mysql.sock
skip-locking
skip-name-resolve
local-infile
set-variable    = max_connections=650
set-variable    = key_buffer=128M
set-variable    = max_allowed_packet=5M
set-variable    = table_cache=512
set-variable    = sort_buffer=2M
set-variable    = record_buffer=1M
set-variable    = myisam_sort_buffer_size=64M
set-variable    = thread_cache=8
set-variable    = thread_concurrency=8  # Try number of CPU's*2
myisam-recover  = BACKUP,FORCE

innodb_data_home_dir = /usr/local/mysql/innobase_var/innobase_data/
innodb_data_file_path = ibdata1:2000M
set-variable = innodb_mirrored_log_groups=1
innodb_log_group_home_dir = /usr/local/mysql/innobase_var/innobase_logs/
set-variable = innodb_log_files_in_group=5
set-variable = innodb_log_file_size=30M
set-variable = innodb_log_buffer_size=10M
innodb_flush_log_at_trx_commit=0
innodb_log_arch_dir = /usr/local/mysql/innobase_var/innobase_logs/
innodb_log_archive=0
set-variable = innodb_buffer_pool_size=256M
set-variable = innodb_additional_mem_pool_size=10M
set-variable = innodb_file_io_threads=8
set-variable = innodb_lock_wait_timeout=50
innodb_fast_shutdown=1  
============================================================================

  Any idea ?

  Regards,
  Alex.

Thread
MySql "fatal error" in mysql-opt.exeMick12 Mar
  • Re: MySql "fatal error" in mysql-opt.exeMiguel Angel Solorzano13 Mar
    • Re: MySql "fatal error" in mysql-opt.exeMichael Widenius19 Mar
      • InnoDB: Assertion failure in thread 10 in file btr0btr.c line 574BAUMEISTER Alexandre19 Mar
Re: InnoDB: Assertion failure in thread 10 in file btr0btr.c line 574Heikki Tuuri19 Mar
Re: InnoDB: Assertion failure in thread 10 in file btr0btr.c line 574Heikki Tuuri19 Mar
  • Re[2]: InnoDB: Assertion failure in thread 10 in file btr0btr.c line 574BAUMEISTER Alexandre19 Mar