Eric, > Please read http://www.mysql.com/doc/en/Using_stack_trace.html and > follow instructions on how to resolve the stack trace. Resolved > stack trace is much more helpful in diagnosing the problem, so please do > resolve it
please use the resolve_stack_dump program in combination with the mysqld.sym which are shipped with the MySQL distro. You may have table corruption. Run CHECK TABLE on your tables. If it prints something to the .err log, please send the output to me. If you have problems starting up mysqld or dumping your tables, see http://www.innodb.com/ibman.html#Forcing_recovery for help. What does uname -a say about your Linux kernel? You should upgrade to a kernel >= 2.4.20 if not yet running one. Earlier Linux kernels seem to cause corruption in many computers. > 030905 20:06:18 InnoDB: Warning: using a partial-field key prefix in > search Any idea what SQL query might be causing the above warning? Do you use LIKE 'abcd%' ? Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ ----- Original Message ----- From: "Eric Aubourg" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Tuesday, September 09, 2003 2:37 AM Subject: bug report > 030905 10:39:38 mysqld started > 030905 10:39:40 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 2 3128426578 > InnoDB: Doing recovery: scanned up to log sequence number 2 3128426578 > InnoDB: Last MySQL binlog file position 0 762953481, file name > ./makiki-bin.016 > 030905 10:39:40 InnoDB: Flushing modified pages from the buffer pool... > 030905 10:39:40 InnoDB: Started > /data/upena/soft/mysql/bin/mysqld: ready for connections. > Version: '4.0.14-max-log' socket: '/tmp/mysql.sock' port: 3306 > 030905 20:06:18 InnoDB: Warning: using a partial-field key prefix in > search > A mysqld process already exists at Sun Sep 7 00:26:58 HST 2003 > A mysqld process already exists at Sun Sep 7 00:27:59 HST 2003 > A mysqld process already exists at Sun Sep 7 00:28:45 HST 2003 > InnoDB: Error: trying to access page number 3422338945 in space 0 > InnoDB: which is outside the tablespace bounds. > InnoDB: Byte offset 0, len 16384, i/o type 10 > 030908 11:27:35 InnoDB: Assertion failure in thread 370700 in file > fil0fil.c line 1176 > InnoDB: Failing assertion: 0 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to [EMAIL PROTECTED] > 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=16777216 > read_buffer_size=131072 > max_used_connections=4 > max_connections=100 > threads_connected=1 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections > = 80383 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > thd=0x884f9d8 > 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... > Cannot determine thread, fp=0xbe3faf68, backtrace may not be correct. > Stack range sanity check OK, backtrace follows: > 0x80d9a90 > 0x40039a24 > 0x82ccda7 > 0x82a0809 > 0x82a0c55 > 0x82937b5 > 0x82c5e24 > 0x82c50e6 > 0x82730d3 > 0x828d7f5 > 0x8284dc0 > 0x8286e3f > 0x821c398 > 0x813b40e > 0x8140e6e > 0x8143631 > 0x80e51cb > 0x80e7fba > 0x80e3483 > 0x80e2edd > 0x80e26ce > 0x40036e17 > 0x40191dda > New value of fp=(nil) failed sanity check, terminating stack trace! > Please read http://www.mysql.com/doc/en/Using_stack_trace.html and > follow instructions on how to resolve the stack trace. Resolved > stack trace is much more helpful in diagnosing the problem, so please do > resolve it > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
