Форум пользователей MySQL

Коллеги, помогите плиз:

У нас стоит Vbulletin 3.8.4 - постоянно слетают одни и теже таблицы, если во время не починить, слетает вся база...

Таблицы: thread, session - причем в пхпмайадмине статус этих таблиц - "используется", после починки становятся нормальные, если непочинить - база отваливается, потом опять все заново...

Вот лог:

-------------------------
Ошибка базы данных в vBulletin 3.8.4:
Invalid SQL:
SELECT IF(visible = 2, 1, 0) AS isdeleted,
thread.*
FROM vb_forum_thread AS thread
WHERE thread.threadid = 33059;

Ошибка MySQL : Table './db_base/_forum_thread' is marked as crashed and should be repaired
Номер ошибки : 145
Дата запроса : Wednesday, November 4th 2009 @ 12:06:05 AM
Дата ошибки : Wednesday, November 4th 2009 @ 12:06:05 AM
Скрипт : http://www.***.ru/_forum/showthread....ewpost&t=33059
Реферрер : http://www.***.ru/_forum/
IP адрес : -------------
Имя пользователя : ***
Имя класса : vB_Database
Версия MySQL : 5.0.51a-community-log
-------------------------

Включили логи MySQL:

--------------------------------------------------------------------------
091109 10:48:35 mysqld started
091109 10:48:36 [Warning] Asked for 196608 thread stack, but got 126976
091109 10:48:36 InnoDB: Started; log sequence number 0 43655
091109 10:48:36 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.51a-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL)
091109 13:17:22 - 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=268435456
read_buffer_size=126976
max_used_connections=15
max_connections=1024
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 389112 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xa682e3f0
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=0xbf7de618, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80a94ae
0x836dd38
0x818a7a7
0x818a772
0x818a735
0x818a6b2
0x818964a
0x8116843
0x80bdcf2
0x80c2a53
0x80ba79b
0x80ba083
0x80b9525
0x836b4ec
0x83959ca
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/us...ack-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 0x8b4bc40 = UPDATE vb_forum_user AS user



thd->thread_id=63280
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
091109 13:17:22 mysqld restarted
091109 13:17:22 [Warning] Asked for 196608 thread stack, but got 126976
091109 13:17:22 InnoDB: Started; log sequence number 0 43655
091109 13:17:23 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.51a-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL)
091109 13:19:03 [ERROR] Got error 134 when reading table './db_lacetticlub3/vb_forum_session'
091109 13:19:08 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './db_lacetticlub3/vb_forum_forumread.MYI'; try to repair it
091109 13:19:08 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './db_lacetticlub3/vb_forum_forumread.MYI'; try to repair it
091109 13:19:08 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './db_lacetticlub3/vb_forum_session.MYI'; try to repair it
091109 13:19:08 [ERROR] Got error 134 when reading table './db_lacetticlub3/vb_forum_session'
091109 13:19:29 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './db_lacetticlub3/vb_forum_session.MYI'; try to repair it
091109 13:19:57 [ERROR] Got error 134 when reading table './db_lacetticlub3/vb_forum_session'
091109 13:19:57 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './db_lacetticlub3/vb_forum_session.MYI'; try to repair it
091109 13:20:03 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './db_lacetticlub3/vb_forum_session.MYI'; try to repair it
091109 13:20:03 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './db_lacetticlub3/vb_forum_session.MYI'; try to repair it
091109 13:20:06 [ERROR] /usr/sbin/mysqld: Table './db_lacetticlub3/vb_forum_forumread' is marked as crashed and should be repaired
091109 13:20:06 [ERROR] /usr/sbin/mysqld: Table './db_lacetticlub3/vb_forum_forumread' is marked as crashed and should be repaired
091109 13:20:07 [ERROR] /usr/sbin/mysqld: Table './db_lacetticlub3/vb_forum_session' is marked as crashed and should be repaired
091109 13:20:07 [ERROR] /usr/sbin/mysqld: Table './db_lacetticlub3/vb_forum_session' is marked as crashed and should be repaired
--------------------------------------------------------------------------
последняя запись еще растягивается на нное кол-во строк, после того, как руками профиксил - все заработало...

Стоит SELinux, MySQL 5.0.51a-community-log

В чем может быть дело? Уже голову сломали ((

Спасибо!

Отредактированно Cyberic (10.11.2009 10:20:29)