Re: MySQL crash.

On Jul 15, 2013, at 4:46 PM, Luis H. Forchesatto wrote:

> Greetings.
> 
> I'm receiving the following error log often on my MySQL database server:
> 
> 130715  8:40:18InnoDB: Assertion failure in thread 2974165904 in file
> btr0cur.c line 160
> InnoDB: Failing assertion: page_is_comp(get_page) == page_is_comp(page)
> InnoDB: We intentionally generate a memory trap.
> InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
> InnoDB: If you get repeated assertion failures or crashes, even
> InnoDB: immediately after the mysqld startup, there may be
> InnoDB: corruption in the InnoDB tablespace. Please refer to
> InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
> InnoDB: about forcing recovery.
> 130715  8:40:18 - 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=327155712
> read_buffer_size=131072
> max_used_connections=19
> max_connections=10000
> threads_connected=6
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
> 3450801 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
> 
> thd=(nil)
> 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=0xb1460fc8, backtrace may not be correct.
> Stack range sanity check OK, backtrace follows:
> 0x81f22d3
> 0x839fb8a
> 0x83a0b0f
> 0x83ab815
> 0x837208e
> 0x8372855
> 0x8373948
> 0x835690a
> 0x83b6cfc
> 0x83397cf
> 0xb7f644fb
> 0xb7d78e5e
> New value of fp=(nil) failed sanity check, terminating stack trace!
> Please read http://dev.mysql.com/doc/mysql/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
> 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.
> 
> As it said it seems to be something related to InnoDB databases, but I got
> no idea on where to start looking for the error.
> 
> Can someone post a troubleshoot for me to follow or contribute with
> speculations?
> 
> -- 
> Att.*
> ***
> Luis H. Forchesatto
> http://br.linkedin.com/pub/luis-henrique-forchesatto/73/684/a67


Dear Mr. Luis,

Report your bug on this site:

http://bugs.mysql.com

Be sure to provide all info that is required of you. Thanks in advance.

--

Pozdrav,

-- 
Sinisa Milivojevic <[email protected]>
MySQL Developer
Larnaca, Republic of Cyprus
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /
 / /|_/ / // /\ \/ /_/ / /__
/_/  /_/\_, /___/\___\_\___/
       <___/   www.mysql.com





-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/bugs