List:General Discussion« Previous MessageNext Message »
From:Heikki Tuuri Date:September 13 2004 6:50am
Subject:Re: MySQL server (4.0.18) crashed with the following error message
View as plain text  
Pandu,

this may be the '4 billion bug'. Please upgrade to 4.0.21, and report if the
crashes persist.

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

Order MySQL technical support from https://order.mysql.com/

----- Original Message ----- 
From: ""Pandu Pabbisetty"" <ppabbisetty@stripped>
Newsgroups: mailing.database.myodbc
Sent: Tuesday, September 07, 2004 10:30 PM
Subject: RE: MySQL server (4.0.18) crashed with the following error message


> ------=_NextPart_000_007F_01C494D6.D6E41300
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> Hi,
>
>
>
> We are running MySQL server 4.0.18.0 and it is occasionally crashing with
> the following kind of errors. We use InnoDB type of tables. Please let us
> know if you have any fix.
>
>
>
> Also, when it encounters this error, it tries to restart/recover itself
but
> fails with a socket "Address already in use" error. It might be useful to
> add/increase appropriate sleep time so that this can get restarted without
> the error.
>
>
============================================================================
> ===
>
> 040907 11:27:35  InnoDB: Assertion failure in thread 22601774 in file
> mem0pool.c line 493
>
> InnoDB: Failing assertion: 0
>
> InnoDB: We intentionally generate a memory trap.
>
> InnoDB: Send a detailed bug report to mysql@stripped
>
> InnoDB: Thread 20791378 stopped in file ha_innodb.cc line 391
>
> 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=0x876735b8, backtrace may not be correct.
>
> Stack range sanity check OK, backtrace follows:
>
> 0x80db9d4
>
> 0x400aaf05
>
> 0x8317861
>
> 0x8316641
>
> 0x821e96e
>
> 0x82214e2
>
> 0x813cc05
>
>
>
> Number of processes running now: 1
>
> mysqld-max process hanging, pid 19997 - killed
>
> 040907 11:27:35  mysqld restarted
>
> 040907 11:27:35  Can't start server: Bind on TCP/IP port: Address already
in
> use
>
> 040907 11:27:35  Do you already have another mysqld server running on
port:
> 3306 ?
>
> 040907 11:27:35  Aborting
>
>
>
> 040907 11:27:35  /usr/sbin/mysqld-max: Shutdown Complete
>
>
>
> 040907 11:27:35  mysqld ended
>
>
>
> Thanks and Regards,
>
> Pandu
>
>
>
>   _____
>
> From: Pandu Pabbisetty [mailto:ppabbisetty@stripped]
> Sent: Tuesday, August 31, 2004 10:05 AM
> To: 'mysql@stripped'
> Subject: MySQL server crashed with the following error message
>
>
>
> Hi,
>
>
>
> Yesterday, our production MySQL server died with the following error
> message. Please let us know if there are any patches for this.
>
>
>
>
>
>
>
> 040830 19:52:13  InnoDB: Assertion failure in thread 27156583 in file
> mem0pool.c line 493
>
> InnoDB: Failing assertion: 0
>
> InnoDB: We intentionally generate a memory trap.
>
> InnoDB: Send a detailed bug report to mysql@stripped
>
> 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=0x877c76d8, backtrace may not be correct.
>
>
>
> Number of processes running now: 1
>
>
>
>
>
> Thanks and Regards,
>
> Pandu R Pabbisetty
>
> Software Architect
>
>
>
> Five9
>
> 7901 Stoneridge Drive, Suite 200
>
> Pleasanton, CA 94588 USA
>
> 925-201-2023 (direct), 925-469-0172 (fax)
>
> pandu@stripped
>
> www.five9.com
>
>
>
> The Leader in Hosted VOIP Contact Center Solutions
>
>
>
>
> ------=_NextPart_000_007F_01C494D6.D6E41300--
>

Thread
RE: MySQL server (4.0.18) crashed with the following error messagePandu Pabbisetty7 Sep
Re: MySQL server (4.0.18) crashed with the following error messageHeikki Tuuri13 Sep