List:General Discussion« Previous MessageNext Message »
From:BAUMEISTER Alexandre Date:January 8 2002 3:38pm
Subject:Assertion failure in thread 54 in file trx0undo.c line 1316
View as plain text  
Bonjour,

  Any idea ?

  I  will try to make the server crash one more time and tell you if I
  find the query.

  Regards,
  Alex.

020108  9:43:58  InnoDB: Started
/opt/mysql/libexec/mysqld: ready for connections
InnoDB: Error: undo->id is 2860816
InnoDB: Assertion failure in thread 54 in file trx0undo.c line 1316
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=67104768
record_buffer=1044480
sort_buffer=2097144
max_used_connections=53
max_connections=100
threads_connected=47
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 372331 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

020108 16:31:20  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 34 1254013465
InnoDB: Doing recovery: scanned up to log sequence number 34 1254078976
InnoDB: Doing recovery: scanned up to log sequence number 34 1254144512
InnoDB: Doing recovery: scanned up to log sequence number 34 1254210048
InnoDB: Doing recovery: scanned up to log sequence number 34 1254275584
InnoDB: Doing recovery: scanned up to log sequence number 34 1254341120
InnoDB: Doing recovery: scanned up to log sequence number 34 1254406656
InnoDB: Doing recovery: scanned up to log sequence number 34 1254472192
InnoDB: Doing recovery: scanned up to log sequence number 34 1254537728
InnoDB: Doing recovery: scanned up to log sequence number 34 1254603264
InnoDB: Doing recovery: scanned up to log sequence number 34 1254668800
InnoDB: After this prints a line for every 10th scan sweep:
InnoDB: Doing recovery: scanned up to log sequence number 34 1255324160
InnoDB: Doing recovery: scanned up to log sequence number 34 1255979520
InnoDB: Doing recovery: scanned up to log sequence number 34 1256634880
InnoDB: Doing recovery: scanned up to log sequence number 34 1257290240
InnoDB: Doing recovery: scanned up to log sequence number 34 1257945600
InnoDB: Doing recovery: scanned up to log sequence number 34 1258600960
InnoDB: Doing recovery: scanned up to log sequence number 34 1259256320
InnoDB: Doing recovery: scanned up to log sequence number 34 1259911680
InnoDB: Doing recovery: scanned up to log sequence number 34 1260567040
InnoDB: Doing recovery: scanned up to log sequence number 34 1261222400
InnoDB: Doing recovery: scanned up to log sequence number 34 1261877760
InnoDB: Doing recovery: scanned up to log sequence number 34 1262533120
InnoDB: Doing recovery: scanned up to log sequence number 34 1263188480
InnoDB: Doing recovery: scanned up to log sequence number 34 1263843840
InnoDB: Doing recovery: scanned up to log sequence number 34 1264499200
InnoDB: Doing recovery: scanned up to log sequence number 34 1265154560
InnoDB: Doing recovery: scanned up to log sequence number 34 1265809920
InnoDB: Doing recovery: scanned up to log sequence number 34 1266465280
InnoDB: Doing recovery: scanned up to log sequence number 34 1267120640
InnoDB: Doing recovery: scanned up to log sequence number 34 1267776000
InnoDB: Doing recovery: scanned up to log sequence number 34 1268431360
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents:0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
24 25 26 27 28 29 30 31 32 33 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
020108 16:32:54  InnoDB: Started
/opt/mysql/libexec/mysqld: ready for connections  

Thread
Assertion failure in thread 54 in file trx0undo.c line 1316BAUMEISTER Alexandre8 Jan
Re: Assertion failure in thread 54 in file trx0undo.c line 1316Heikki Tuuri8 Jan