mysql bug | срочно!



[root@base bin]# ./safe_mysqld &

[1] 4263

[root@base bin]# Starting mysqld daemon with databases from /opt/mysql/var

./safe_mysqld: line 284:  4274 Segmentation fault      $NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --datadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-locking >>$err_log 2>&1

070219 19:33:45  mysqld ended


содержание base.err

070219 19:36:14  mysqld started
070219 19:36:15  InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 11 452549132
InnoDB: Doing recovery: scanned up to log sequence number 11 452549132
InnoDB: Error: trying to access a stray pointer 27f17ff8
InnoDB: buf pool start is at 87f24000, number of pages 32768
070219 19:36:15  InnoDB: Assertion failure in thread 3086571744 in file ../include/buf0buf.ic line 284
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to
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

It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 671339 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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...
Bogus stack limit or frame pointer, fp=0xbfe2a5ec, stack_bottom=0x9080908, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x9080908  is invalid pointer

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 26213 did to cause the crash.  In some cases of really
bad corruption, the values shown above may be invalid

The manual page at contains
information that should help you find out what is causing the crash
070219 19:36:15  mysqld ended

чем вылечить?

Re: mysql bug | срочно!

1. Обновляться до последней версии пробовал?

2. Это оно сразу при запуске грохается или после какого-то запроса?

gods-little-toy ★★★ ()

Re: mysql bug | срочно!

Настройки использования памяти в /etc/my.cnf уменьши. Скорей всего не хватает памяти.

UncleAndy ★★★ ()
Ответ на: Re: mysql bug | срочно! от george_root

Re: mysql bug | срочно!

1. Проверяй железо. Особенно память. 2. Если возможно - сделай mysqldump базы и восстанови ее с нуля (старую базу лучше сохранить до окончательного восстановления).

UncleAndy ★★★ ()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.