List:General Discussion« Previous MessageNext Message »
From:Daniel da Veiga Date:June 8 2006 2:08am
Subject:Re: MySQL crashes
View as plain text  
On 6/7/06, Ian Collins <ian.collins@stripped> wrote:
> I have a site running MySQL 4.1.19.
> When I was first given the problem, the site only stayed up for a couple
> of days - they then found they had to reboot (as opposed to just
> restarting MySQL).
> The error message they were getting is below (between the snip's).
> After looking at the site, I altered some my.cnf parameters, and then
> the site stayed up for 14 days before doing the same.
> This site is identical to others I have seen - that are running with no
> issues.
> Could this be hardware (memory related)?
> Regards,
> Ian Collins.
> ============================================ snip
> =======================================
> Version: '4.1.9-standard'  socket: '/tmp/mysql.sock'  port: 3306
> Official MySQL RPM
> 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=134217728
> read_buffer_size=131072
> max_used_connections=80
> max_connections=400
> threads_connected=68
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
> = 1001468 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
> thd=0x8e6d0c0
> 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=0xbfb1f5d8, backtrace may not be correct.
> Stack range sanity check OK, backtrace follows:
> 0x808e1b7
> 0x82e5a08
> 0x80b68f6
> 0x804c0bd
> 0x804bfb3
> 0x808473c
> 0x808ddb3
> 0x809b8e6
> 0x82e31bc
> 0x830ca8a
> New value of fp=(nil) failed sanity check, terminating stack trace!
> Please read 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 (nil)  is invalid pointer
> thd->thread_id=52266
> The manual page at contains
> information that should help you find out what is causing the crash.
> Number of processes running now: 0
> ============================================ snip
> =======================================

You mean 4.1.9, not 4.1.19 right? Try upgrading your server to the
latest 4.1, I believe its 4.1.20, and report back... I`ve seen various
issues with versions below 4.1.12...

Daniel da Veiga
Computer Operator - RS - Brazil
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
MySQL crashesIan Collins8 Jun
  • Re: MySQL crashesDaniel da Veiga8 Jun
    • Re: MySQL crashesDilipkumar8 Jun