SDiZ Cheng writes:
> I cannot find the core file.. where is it?
> BTW, system seems somtimes run out of file handles / max processes.
> There is some more information to provide:
> 
> mysqld got signal 11;
> The manual section 'Debugging a MySQL server' tells you how to use a
> stack trace and/or the core file to produce a readable backtrace that may
> help in finding out why mysqld died
> Attemping 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, ebp=0xbffff3d8, backtrace may not be correct
> stack range sanity check, ok, backtrace follows
> 0x40078dd4 _end + 937886004
> 0x40077f05 _end + 937882213
> 0x80afda1 create_new_thread__FP3THD + 937
> 0x80b03a5 handle_connections_sockets__FPv + 1185
> 0x80af6a7 main + 2539
> 0x4010b2db _end + 938485307
> 0x8089971 _start + 33
> New value of ebp failed sanity check terminating backtrace
> 
> Number of processes running now: 0
> 010613 22:29:24  mysqld restarted
> /usr/local/mysql/libexec/mysqld: ready for connections
> 010613 22:29:25  Warning: Checking table:   './Counter/common_one_IP'
> 010613 22:29:25  Warning: Checking table:   './Counter/common_one'
> 010613 22:29:29  Warning: Checking table:   './user/log'
> 010613 22:29:29  Warning: Checking table:   './Counter/taikoo_taikoo_IP'
> 010613 22:29:29  Warning: Checking table:   './Counter/taikoo_taikoo'
> mysqld got signal 11;
> The manual section 'Debugging a MySQL server' tells you how to use a
> stack trace and/or the core file to produce a readable backtrace that may
> help in finding out why mysqld died
> Attemping 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, ebp=0xbffff3d8, backtrace may not be correct
> stack range sanity check, ok, backtrace follows
> 0x40078dd4 _end + 937886004
> 0x40077f05 _end + 937882213
> 0x80afda1 create_new_thread__FP3THD + 937
> 0x80b03a5 handle_connections_sockets__FPv + 1185
> 0x80af6a7 main + 2539
> 0x4010b2db _end + 938485307
> 0x8089971 _start + 33
> New value of ebp failed sanity check terminating backtrace
> 
> Number of processes running now: 0
> 010613 22:29:56  mysqld restarted
> /usr/local/mysql/libexec/mysqld: ready for connections
> 


HI!

core file, if created is in datadir directory.

The above looks like it is caused either by imperfect build of 
MySQl or by corrupted tables. Use our binary for Linux and check
tables for corruption.


Regards,

For technical support contracts, go to https://order.mysql.com/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Mr. Sinisa Milivojevic <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, FullTime Developer
/_/  /_/\_, /___/\___\_\___/   Larnaca, Cyprus
       <___/   www.mysql.com

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to