Philipp,
----- Original Message -----
From: "Philipp Steinkrüger" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, March 31, 2004 3:59 PM
Subject: Mysql 4.0.18 crashed6384512
> ------=_NextPart_000_002D_01C4172E.C75E7F90
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> Hi,
>
>
> today our mysql server 4.0.18-standard (binary) crashed.
> I found a similar report (InnoDB: Assertion failure in thread), but it
> was with 4.0.16 and one reply said that the bug was fixed in 4.0.17.
>
> Here is the report from mysql.err:
>
> InnoDB: Started
> /usr/local/mysql/bin/mysqld: ready for connections.
> Version: '4.0.18-standard' socket: '/var/run/mysql/mysql.sock' port: =
> 3306
> InnoDB: Error: Mem area size is 0. Possibly a memory overrun of the
> InnoDB: previous allocated area!
> InnoDB: Apparent memory corruption: mem dump len 500; hex =
> 666e6f7264f77318750f0a0d0805140f06090a0f07080b08000035fd00001cc600008f690=
> 0011c0e0000250280001239ffeb6be40d0d0f0f140f0a0b0f0d0a31313232333334343535=
> 363638383838050004050b000000000003000000000000ff0000818181426c756d656e6b6=
> 96e646572800000003d0300000000140a0a0a00800000000000190a000000000000000000=
> 00633a2f44572f64770000000000028d00004d00858985870000000000000000777318d70=
> 00000000000000000d0f56d94d0f56da1d0f56daed0f56dbbd0f56dc8d0f56dd5d0f56de2=
> d0f56defd0f56dfcd0f56d09d1f56d16d1f56d23d1f56d30d1f56d9900000000000000107=
> bf26d90000000f63d775f9268a520773073656c2e6300a208000000000000000000000000=
> 0000000000000000000080000000000000000000000040000000400000000000000001300=
> 1303c623e3c693e636869736c656167202d2030342e30332e323030342031383a32352055=
> 68723a3c2f693e3c2f423e3c62723e646174756d20e46e6465726ef56d98000000d905000=
> 0008e4172f8e1ec6dd0050000f63d775fb307952d78307472782e63008b000000640bf56d=
> 720bf56d800bf56d8813da70207bf26dc00500000100000000000000c0050000400000000=
> 0000000fe0bf56d70bbdc700816da70c875f26d250000000000; asc =
> fnord.s.u.................5........i......%....9..k............1122334455=
> 668888.......................Blumenkinder....=3D.........................=
> ...c:/DW/dw.........M.............ws.............m...m...m...m...m...m...=
> m...m...m...m...m...m#..m0..m.........{.m.....=3Dw_.h. =
> [EMAIL PROTECTED]@........0.0<b><i>chislea=
> g - 04.03.2004 18:25 Uhr:</i></B><br>datum =
> .ndern.m..........Ar...m.....=3Dw_...-x0trx.c.....d..mr..m...m...p =
> [EMAIL PROTECTED];
> InnoDB: Scanning backward trying to find previous allocated mem blocks
> Mem block at - 600, file w0sel.c, line 2273
> Freed mem block at - 1352, file x0trx.c, line 153
> Freed mem block at - 1696, file x0trx.c, line 139
> Freed mem block at - 21496, file w0sel.c, line 2210
> Freed mem block at - 27600, file x0trx.c, line 139
> Freed mem block at - 30632, file w0sel.c, line 2210
> Freed mem block at - 40648, file w0sel.c, line 2210
> Freed mem block at - 40840, file x0trx.c, line 153
> Freed mem block at - 42088, file x0trx.c, line 153
> Freed mem block at - 42432, file x0trx.c, line 139
> InnoDB: Scanning forward trying to find next allocated mem blocks
> Freed mem block at + 16, file w0sel.c, line 2210
> Mem block at + 168, file x0trx.c, line 139
> Mem block at + 1664, file x0trx.c, line 139
> Freed mem block at + 4696, file w0sel.c, line 2210
> Freed mem block at + 28800, file x0trx.c, line 139
> Freed mem block at + 29144, file x0trx.c, line 153
> Freed mem block at + 30712, file 0data.c, line 153
> Freed mem block at + 31304, file 0data.c, line 153
> Freed mem block at + 31632, file w0sel.c, line 2210
> Freed mem block at + 774912, file x0trx.c, line 78
> 040316 16:14:06 InnoDB: Assertion failure in thread 727081009 in file =
> mem0pool.c line 493
> 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=3D134217728
> read_buffer_size=3D8384512
> max_used_connections=3D246
> max_connections=3D350
> threads_connected=3D6
> It is possible that mysqld could use up to=20
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
> =3D 952965 K
> bytes of memory=20
> Hope that's ok; if not, decrease some variables in the equation.
>
> thd=3D0x63adfe60
> 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=3D0xbf99ebd8, backtrace may not be correct.
> Stack range sanity check OK, backtrace follows:
> 0x80705d0
> 0x8297878
> 0x822837c
> 0x82271d1
> 0x81322fd
> 0x8137047
> 0x80cbe07
> 0x80cc05f
> 0x80c0f79
> 0x80a6ce6
> 0x807c382
> 0x807e9ba
> 0x807a0c3
> 0x8079b1d
> 0x8079359
> 0x829502c
> 0x82be82a
> New value of fp=3D(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
> Trying to get some variables.
> Some pointers may be invalid and cause the dump to abort...
> thd->query at 0x6f3de920 is invalid pointer
> thd->thread_id=3D31294926
> The manual page at http://www.mysql.com/doc/en/Crashing.html contains
> information that should help you find out what is causing the crash.
> 040316 16:27:10 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 3044349028
> InnoDB: Doing recovery: scanned up to log sequence number 0 3044402982
> 040316 16:27:10 InnoDB: Starting an apply batch of log records to the =
> database...
> InnoDB: Progress in percents: 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=20
> InnoDB: Apply batch completed
you should run RAM tests on your computer.
People sometimes report these memory corruption assertion failures, but
since there is no pattern in them, it is hard to look for a bug in InnoDB.
In this particular case, 4 zero bytes have appeared where there should be
the length of an InnoDB memory block.
> Regards,
> Philipp
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
Register now for the 2004 MySQL Users Conference!
http://www.mysql.com/events/uc2004/index.html
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
