Hello.
Are you using an official binary? Was there any error messages
before crashing? Resolve the stack trace. Follow recomendations from:
http://www.mysql.com/doc/en/Crashing.html
"Jack" <jiangpeirong@stripped> wrote:
> hi,all.
>
> i can't start mysqld anymore , it's log reports below:
> 050503 00:09:58 mysqld started
> 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=16384
> read_buffer_size=131072
> max_used_connections=0
> max_connections=100
> threads_connected=0
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 19215 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=0x40035158, backtrace may not be correct.
> Stack range sanity check OK, backtrace follows:
> 0x814aecd
> 0x40035450
> (nil)
> 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. Reso
> lved
> 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.
> 050503 00:09:58 mysqld ended
>
>
> and i try to run mysql_install_db the backtrace is still 0x814aecd ..
>
> and i haven't found any one else has met this problem . so any suggestion ?
>
>
> i believe that thereis something wrong with my.cnf or i havn'e set some variable of
> it, because i have succeed starting the mysqld before my system has been cracked . and
> don't
> think that the system has some problem , the system i backup from the system that the
> mysqld has been started before.
>
> see my my.cnf:
> [mysqld]
> datadir=/var/lib/mysql
> socket=/var/lib/mysql/mysql.sock
> skip-locking
> set-variable = key_buffer_size=16K
> set-variable = max_allowed_packet=1M
> set-variable = thread_stack=64K
> set-variable = table_cache=4
> set-variable = sort_buffer=64K
> set-variable = net_buffer_length=2K
>
> # Default to using old password format for compatibility with mysql 3.x
> # clients (those using the mysqlclient10 compatibility package).
> old_passwords=1
> skip-innodb
> skip-bdb
> [mysql.server]
> user=mysql
> basedir=/var/lib
>
> [mysqld_safe]
> err-log=/var/log/mysqld.log
> pid-file=/var/run/mysqld/mysqld.pid
>
> jack
>
>
>
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenko@stripped
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com
