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

Коллеги доброе утро!
Возникла проблема с mysql, в котором я разбираюсь очень мало т.к. ставил его только лишь для Zabbix, как говорится установил и забыл. Но сегодня с утра возникли проблемы начала постоянно отваливаться mysql(постоянно ребутается)

uname -a
FreeBSD zabbix 8.1-RELEASE

df

Filesystem  1K-blocks     Used     Avail Capacity  Mounted on
/dev/ad4s1a    507630   172986    294034    37%    /
devfs               1        1         0   100%    /dev
/dev/ad4s1e    507630    17282    449738     4%    /tmp
/dev/ad4s1f 143299754 14420310 117415464    11%    /usr
/dev/ad4s1d   3025550  1534554   1248952    55%    /var

В логах пишет следующее:

cat /var/db/mysql/zabbix.err

120207 10:44:20 - mysqld got signal 6 ;
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=8384512
read_buffer_size=131072
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337711 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

120207 10:44:20 mysqld_safe mysqld restarted
120207 10:44:20 [Note] Plugin 'FEDERATED' is disabled.
120207 10:44:20  InnoDB: Initializing buffer pool, size = 8.0M
120207 10:44:20  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 64 2581012662
120207 10:44:20  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 64 2581038282
120207 10:44:20  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
120207 10:44:20  InnoDB: Started; log sequence number 64 2581038282
120207 10:44:20 [Note] Event Scheduler: Loaded 0 events
120207 10:44:20 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.1.54'  socket: '/tmp/mysql.sock'  port: 3306  FreeBSD port: mysql-server-5.1.54_1
120207 10:44:21  InnoDB: Assertion failure in thread 709101056 in file btr/btr0cur.c line 163
InnoDB: Failing assertion: btr_page_get_next(get_page, mtr) == buf_frame_get_page_no(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/ … overy.html
InnoDB: about forcing recovery.

И так по кругу каждую секунду ... *(

Заранее спасибо за любую помощь!