List:General Discussion« Previous MessageNext Message »
From:Michael Widenius Date:January 30 2000 8:06am
Subject:Strange fallover
View as plain text  
Hi!

>>>>> "TTSG" == TTSG  <ttsg@stripped> writes:

TTSG> Hi,
TTSG> 	All of a sudden our monitoring showed that the server wasn't running
TTSG> anymore. Looking at the machine, it appeared that safe_mysqld wasn't running
TTSG> either. How strange!

TTSG> 	The log shows nothing special :

TTSG> mysqld started on  Sat Jan 8 11:58:43 EST 2000
TTSG> 000108 11:58:43  Warning: setrlimit returned ok, but didn't change limits. Max
> open files is 6668
TTSG> 000108 11:58:43  Warning: Changed limits: max_connections: 1331  table_cache:
> 2663
TTSG> /usr/local/libexec/mysqld: ready for connections
TTSG> mysqld ended on  Thu Jan 27 14:17:58 EST 2000

TTSG> GDB shows :

TTSG> jarnsaxa# gdb /usr/local/libexec/mysqld mysqld.core       
TTSG> GNU gdb 
TTSG> Copyright 1998 Free Software Foundation, Inc.
TTSG> GDB is free software, covered by the GNU General Public License, and you are
TTSG> welcome to change it and/or distribute copies of it under certain conditions.
TTSG> Type "show copying" to see the conditions.
TTSG> There is absolutely no warranty for GDB.  Type "show warranty" for details.
TTSG> This GDB was configured as "i386-unknown-bsdi4.0.1"...
TTSG> Core was generated by `mysqld'.
TTSG> Program terminated with signal 11, Segmentation fault.
TTSG> #0  0x808bd50 in get_best_combination ()
TTSG> (gdb) bt
TTSG> #0  0x808bd50 in get_best_combination ()
TTSG> #1  0x808a723 in make_join_statistics ()
TTSG> #2  0x80892ad in mysql_select ()
TTSG> #3  0x80764fc in mysql_execute_command ()
TTSG> #4  0x8077ba2 in mysql_parse ()
TTSG> #5  0x8075cd7 in do_command ()
TTSG> #6  0x807585b in handle_one_connection ()
TTSG> #7  0xc1f4868 in _thread_kern_start ()

TTSG> 	Any ideas? (/usr/local/libexec/mysqld  Ver 3.22.27 for pc-bsdi4.0.1 on i386)

Could you try upgrading to MySQL 3.22.30 and compiling it with
--with-debug.  If 3.22.30 still fails, you should then be able to get
the line number where this happens;  This would help us locate and fix
the bug.

Regards,
Monty

Thread
Strange falloverTTSG27 Jan
  • Re: Strange falloversasha28 Jan
    • Re: Strange falloverTTSG28 Jan
  • Strange falloverMichael Widenius30 Jan