List:General Discussion« Previous MessageNext Message »
From:Lior Nisim Date:March 3 2004 12:02pm
Subject:RE: Mysql 4.1.1 crashes
View as plain text  
Hi

Here is the stack trace :
0x8106af3 handle_segfault + 423
0x40047a65 _end + 933903229
0x832b873 lock_clust_rec_cons_read_sees + 111
0x82774fc row_search_for_mysql + 9884
0x81783cb general_fetch__11ha_innobasePcUiUi + 75
0x8178496 index_next_same__11ha_innobasePcPCcUi + 34
0x813eecc join_read_next_same__FP14st_read_record + 52
0x813e57e sub_select__FP4JOINP13st_join_tableb + 330
0x813e226 do_select__FP4JOINPt4List1Z4ItemP8st_tableP9Procedure + 434
0x8134b36 exec__4JOIN + 4234
0x8135068
mysql_select__FP3THDPPP4ItemP13st_table_listUiRt4List1Z4ItemP4ItemUiP8st
_orderT7T5T7UlP13select_resultP18st_select_lex_unitP13s + 832
0x8131fde handle_select__FP3THDP6st_lexP13select_result + 174
0x81142b7 mysql_execute_command__FP3THD + 1427
0x8118d49 mysql_parse__FP3THDPcUi + 177
0x8112f3f dispatch_command__F19enum_server_commandP3THDPcUi + 1635
0x81128d1 do_command__FP3THD + 161
0x8112047 handle_one_connection + 563
0x40044c3f _end + 933891415
0x401b5b2a _end + 935402562 

Thanks
Lior

-----Original Message-----
From: vpendleton@stripped [mailto:vpendleton@stripped] 
Sent: Tuesday, March 02, 2004 10:08 PM
To: Nisim, Lior
Cc: mysql@stripped
Subject: Re: Mysql 4.1.1 crashes

Did you run a stack trace?

>>>>>>>>>>>>>>>>>> Original Message
> <<<<<<<<<<<<<<<<<<

On 3/2/04, 9:02:15 AM, "Nisim," Lior <lior.nisim@stripped> wrote
regarding 
Mysql 4.1.1 crashes:


> hi

> My server crashes on sub qurey , can any one help ?

>
------------------------------------------------------------------------
> ---------------------------
> 040302 16:32:20  mysqld started
> 040302 16:32:20  InnoDB: Started; log sequence number 0 60169
> /tmp/mysql/mysql_4.1.1/bin/mysqld: ready for connections.
> Version: '4.1.1-alpha-max'  socket: '/tmp/mysql.sock'  port: 3306
> 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
> read_buffer_size=131072
> max_used_connections=0
> max_connections=100
> threads_connected=1
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections
> = 225791 K
> bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.

> thd=0x867e9a0
> 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=0x424a6838, backtrace may not be correct.
> Stack range sanity check OK, backtrace follows:
> 0x8106af3
> 0x40047a65
> 0x832b873
> 0x82774fc
> 0x81783cb
> 0x8178496
> 0x813eecc
> 0x813e57e
> 0x813e226
> 0x8134b36
> 0x8135068
> 0x8131fde
> 0x81142b7
> 0x8118d49
> 0x8112f3f
> 0x81128d1
> 0x8112047
> 0x40044c3f
> 0x401b5b2a
> New value of fp=(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 0x8685398 = SELECT milestone,date,user,notes FROM
> milestones_info WHERE block='agadderc' group by milestone having
> date=(SELECT max(date) FROM milestones_info as tmp WHERE
> block='agadderc' AND milestone=tmp.milestone)
> thd->thread_id=1
> 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.

> Number of processes running now: 0
> 040302 16:32:31  mysqld restarted
> 040302 16:32:31  InnoDB: Started; log sequence number 0 60169
> /tmp/mysql/mysql_4.1.1/bin/mysqld: ready for connections.
> Version: '4.1.1-alpha-max'  socket: '/tmp/mysql.sock'  port: 3306

>
------------------------------------------------------------------------
> ---------------------------


> >Description:
>     mysql crashes on sub query
> >How-To-Repeat:
>   check the below error log
> >Fix:
>  <how to correct or work around the problem, if known (multiple
lines)>

> >Submitter-Id:
> >Originator:
> >Organization:
>  <organization of PR author (multiple lines)>
> >MySQL support: [none | licence | email support | extended email
support
> ]
> >Synopsis: <synopsis of the problem (one line)>
> >Severity: <[ non-critical | serious | critical ] (one line)>
> >Priority: <[ low | medium | high ] (one line)>
> >Category: mysql
> >Class:  <[ sw-bug | doc-bug | change-request | support ] (one line)>
> >Release: mysql-4.1.1-alpha-max (Official MySQL-max binary)

> >C compiler:    2.95.3
> >C++ compiler:  2.95.3
> >Environment:
>  <machine, os, target, libraries (multiple lines)>
> System: Linux iapp003 2.4.9-45lxset11 #1 Mon Jan 5 17:10:26 MST 2004
> i686 unknown
> Architecture: i686

> Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc
> /usr/bin/cc
> GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
> gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-85)
> Compilation info: CC='gcc'  CFLAGS='-O2 -mpentiumpro -DBIG_TABLES'
> CXX='gcc'  CXXFLAGS='-O2 -mpentiumpro -felide-constructors
-DBIG_TABLES'
> LDFLAGS=''  ASFLAGS=''
> LIBC:
> lrwxrwxrwx    1 root     root           13 Jun 18  2003 /lib/libc.so.6
> -> libc-2.2.4.so
> -rwxr-xr-x    1 root     root      1285884 Mar  6  2003
> /lib/libc-2.2.4.so
> -rw-r--r--    1 root     root     27338566 Mar  6  2003
/usr/lib/libc.a
> -rw-r--r--    1 root     root          178 Mar  6  2003
/usr/lib/libc.so
> Configure command: ./configure '--prefix=/usr/local/mysql'
> '--localstatedir=/usr/local/mysql/data'
> '--libexecdir=/usr/local/mysql/bin' '--with-comment=Official MySQL-max
> binary' '--with-extra-charsets=complex' '--with-server-suffix=-max'
> '--enable-thread-safe-client' '--enable-local-infile'
> '--enable-assembler' '--disable-shared' '--with-berkeley-db'
> '--with-raid' '--with-readline' '--with-embedded-server'
'--with-innodb'
> 'CFLAGS=-O2 -mpentiumpro -DBIG_TABLES' 'CXXFLAGS=-O2 -mpentiumpro
> -felide-constructors -DBIG_TABLES' 'CXX=gcc'



> Lior Nisim

> lior.nisim@stripped
Thread
Mysql 4.1.1 crashesLior Nisim2 Mar
  • Re: Mysql 4.1.1 crashesvpendleton2 Mar
  • Re: Mysql 4.1.1 crashesVictoria Reznichenko3 Mar
RE: Mysql 4.1.1 crashesLior Nisim3 Mar
RE: Mysql 4.1.1 crashesHeikki Tuuri3 Mar