Okay :) Here is the starting of the log, before the infinite loop...
070620 15:17:52 mysqld started 070620 15:17:52 mysqld started 070620 15:17:53 mysqld ended 070620 15:17:54 InnoDB: Out of memory in additional memory pool. InnoDB: InnoDB will start allocating memory from the OS. InnoDB: You may get better performance if you configure a bigger InnoDB: value in the MySQL my.cnf file for InnoDB: innodb_additional_mem_pool_size. 070620 15:17:54 InnoDB: Out of memory in additional memory pool. InnoDB: InnoDB will start allocating memory from the OS. InnoDB: You may get better performance if you configure a bigger InnoDB: value in the MySQL my.cnf file for InnoDB: innodb_additional_mem_pool_size. 070620 15:17:55 InnoDB: Started 070620 15:17:55 InnoDB: Started /usr/libexec/mysqld: ready for connections /usr/libexec/mysqld: ready for connections 070620 15:18:56 mysqld started 070620 15:18:56 InnoDB: Out of memory in additional memory pool. InnoDB: InnoDB will start allocating memory from the OS. InnoDB: You may get better performance if you configure a bigger InnoDB: value in the MySQL my.cnf file for InnoDB: innodb_additional_mem_pool_size. 070620 15:18:56 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 973668639 InnoDB: Doing recovery: scanned up to log sequence number 0 973668639 070620 15:18:56 InnoDB: Flushing modified pages from the buffer pool... 070620 15:18:56 InnoDB: Started /usr/libexec/mysqld: ready for connections InnoDB: Error: trying to access page number 629914496 in space 0 InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10 070622 4:14:23 InnoDB: Assertion failure in thread 114696 in file fil0fil.c line 1171 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to mysql@lists.mysql.com 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=8388600 record_buffer=131072 sort_buffer=2097144 max_used_connections=41 max_connections=80 threads_connected=40 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 182271 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... Cannot determine thread, fp=0x42d36f08, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80ee059 0x4a50efd6 0x827f18e 0x825615d 0x8256500 0x824ce2e 0x8234b2a 0x8235254 0x8235803 0x82030ca 0x820338b 0x81f00e7 0x81efce7 0x8235d70 0x81f46d1 0x4a509cce 0x4a463b3a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/U/s/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 The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash Number of processes running now: 34 mysqld process hanging, pid 141 - killed mysqld process hanging, pid 30110 - killed mysqld process hanging, pid 4210 - killed mysqld process hanging, pid 20023 - killed mysqld process hanging, pid 27208 - killed mysqld process hanging, pid 8714 - killed mysqld process hanging, pid 9914 - killed mysqld process hanging, pid 8435 - killed mysqld process hanging, pid 1023 - killed mysqld process hanging, pid 728 - killed mysqld process hanging, pid 26602 - killed mysqld process hanging, pid 17526 - killed mysqld process hanging, pid 1176 - killed mysqld process hanging, pid 9107 - killed mysqld process hanging, pid 29767 - killed mysqld process hanging, pid 11378 - killed mysqld process hanging, pid 10440 - killed mysqld process hanging, pid 11665 - killed Number of processes running now: 0 070622 04:14:26 mysqld restarted 070622 04:14:26 mysqld restarted Number of processes running now: 0 070622 04:14:26 mysqld restarted 070622 4:14:28 InnoDB: Out of memory in additional memory pool. InnoDB: InnoDB will start allocating memory from the OS. InnoDB: You may get better performance if you configure a bigger InnoDB: value in the MySQL my.cnf file for InnoDB: innodb_additional_mem_pool_size. 070622 4:14:28 InnoDB: Out of memory in additional memory pool. InnoDB: InnoDB will start allocating memory from the OS. InnoDB: You may get better performance if you configure a bigger InnoDB: value in the MySQL my.cnf file for InnoDB: innodb_additional_mem_pool_size. 070622 4:14:28 InnoDB: Out of memory in additional memory pool. InnoDB: InnoDB will start allocating memory from the OS. InnoDB: You may get better performance if you configure a bigger InnoDB: value in the MySQL my.cnf file for InnoDB: innodb_additional_mem_pool_size. 070622 4:14:36 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 973756261 070622 4:14:36 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 973756261 070622 4:14:36 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 973756261 InnoDB: Doing recovery: scanned up to log sequence number 0 973834124 InnoDB: Doing recovery: scanned up to log sequence number 0 973834124 InnoDB: Doing recovery: scanned up to log sequence number 0 973834124 070622 4:14:37 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 070622 4:14:37 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 070622 4:14:37 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 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 InnoDB: Apply batch completed InnoDB: Apply batch completed 070622 4:14:39 InnoDB: Flushing modified pages from the buffer pool... 070622 4:14:39 InnoDB: Flushing modified pages from the buffer pool... 070622 4:14:39 InnoDB: Flushing modified pages from the buffer pool... 070622 4:14:39 InnoDB: Started 070622 4:14:39 InnoDB: Started 070622 4:14:40 InnoDB: Started 070622 4:14:40 InnoDB: Assertion failure in thread 114696 in file fsp0fsp.c line 2945 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to mysql@lists.mysql.com 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 etc... etc... :/ Hope this will help... It's an old MySQL 3. Thanks :) ----- Message d'origine ---- De : Ananda Kumar <[EMAIL PROTECTED]> À : Julien Marchand <[EMAIL PROTECTED]> Cc : mysql@lists.mysql.com Envoyé le : Vendredi, 22 Juin 2007, 16h31mn 15s Objet : Re: Re : InnoDB: Assertion failure - MySQL keeps crashing I had this issue, so just wanted to know, even if you have the same error message. regards anandkl On 6/22/07, Julien Marchand <[EMAIL PROTECTED]> wrote: No, I don't have this error :/ And not any file system full issue... ----- Message d'origine ---- De : Ananda Kumar <[EMAIL PROTECTED]> À : Julien Marchand <[EMAIL PROTECTED]> Cc : mysql@lists.mysql.com Envoyé le : Vendredi, 22 Juin 2007, 13h45mn 12s Objet : Re: InnoDB: Assertion failure - MySQL keeps crashing Hi Julien, Do you see any "InnoDB: using the same InnoDB data or log files. >> InnoDB: Unable to lock /var/lib/mysql/ibdata1, error: 11 >> InnoDB: Check that you do not already have another mysqld process >> InnoDB: using the same InnoDB data or log files." of these error in the error log file. Was there any file system full issue. On 6/22/07, Julien Marchand <[EMAIL PROTECTED]> wrote: > > Hello, > > > > My MySQL keeps crashing and restarting, and I get this log, which > repeats indefinitely: > > > > Number of processes running now: 0 > > 070622 13:01:46 mysqld restarted > > 070622 13:01:46 InnoDB: Out of memory in additional memory pool. > > InnoDB: InnoDB will start allocating memory from the OS. > > InnoDB: You may get better performance if you configure a bigger > > InnoDB: value in the MySQL my.cnf file for > > InnoDB: innodb_additional_mem_pool_size. > > 070622 13:01:46 InnoDB: Starting an apply batch of log records to the > database... > > InnoDB: Progress in percents: 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 > > 070622 13:01:47 InnoDB: Started > > /usr/libexec/mysqld: ready for connections > > 070622 13:01:48 InnoDB: Assertion failure in thread 114696 in file > fsp0fsp.c line 2945 > > InnoDB: We intentionally generate a memory trap. > > InnoDB: Send a detailed bug report to mysql@lists.mysql.com 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=8388600 > > record_buffer=131072 > > sort_buffer=2097144 > > max_used_connections=0 > > max_connections=80 > > threads_connected=0 > > It is possible that mysqld could use up to key_buffer_size + > (record_buffer + sort_buffer)*max_connections = 182271 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... > > Cannot determine thread, fp=0x42d36f98, backtrace may not be correct. > > Stack range sanity check OK, backtrace follows: > > 0x80ee059 > > 0x4a50efd6 > > 0x8273f32 > > 0x8234054 > > 0x8234654 > > 0x8234874 > > 0x823589b > > 0x82030ca > > 0x820338b > > 0x81f00e7 > > 0x81efce7 > > 0x8235d70 > > 0x81f4c15 > > 0x4a509cce > > 0x4a463b3a > > New value of fp=(nil) failed sanity check, terminating stack trace! > > Please read http://www.mysql.com/doc/U/s/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 The > manual page at http://www.mysql.com/doc/C/r/Crashing.html contains > information that should help you find out what is causing the crash > > > > Number of processes running now: 0 > > 070622 13:01:48 mysqld restarted > > 070622 13:01:48 InnoDB: Out of memory in additional memory pool. > > InnoDB: InnoDB will start allocating memory from the OS. > > InnoDB: You may get better performance if you configure a bigger > > InnoDB: value in the MySQL my.cnf file for > > InnoDB: innodb_additional_mem_pool_size. > > 070622 13:01:48 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 974975241 > > InnoDB: Doing recovery: scanned up to log sequence number 0 974975241 > > 070622 13:01:48 InnoDB: Flushing modified pages from the buffer pool... > > 070622 13:01:48 InnoDB: Started > > /usr/libexec/mysqld: ready for connections > > 070622 13:01:49 InnoDB: Assertion failure in thread 114696 in file > fsp0fsp.c line 2945 > > InnoDB: We intentionally generate a memory trap. > > InnoDB: Send a detailed bug report to mysql@lists.mysql.com mysqld got > signal 11; > .............................. > > > > > > When I comment out the InnoDB configuration line, InnoDB doesn't start > and MySQL can start normally. > > > > But all the InnoDB tables can't be accessed... > > > > Do you have an idea in how to fix this problem ? Sorry for my English, > but I'm French ^_^ > > > > Thanks :) > > > > > > _____________________________________________________________________________ > Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! > Mail > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > ______________________________________________________________________________ Stockage illimité de vos mails avec Yahoo! Mail. Changez aujourd'hui de mail ! _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
