- 论坛徽章:
- 0
|
日志如下
080314 14:46:45 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 216, event_type: 2
080314 14:46:45 [Note] Starting crash recovery...
080314 14:46:45 InnoDB: Starting recovery for XA transactions...
080314 14:46:45 InnoDB: Transaction 0 11353655 in prepared state after recovery
080314 14:46:45 InnoDB: Transaction contains changes to 1 rows
080314 14:46:45 InnoDB: 1 transactions in prepared state after recovery
080314 14:46:45 [Note] Found 1 prepared transaction(s) in InnoDB
InnoDB: Starting in background the rollback of uncommitted transactions
080314 14:46:45 InnoDB: Rolling back trx with id 0 11354122, 1 rows to undo
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=0
read_buffer_size=258048
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 = 76399 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
系统是FB6.2,版本是5.0.22
有遇到这种情况的吗?有解决办法吗? |
|