Debian testing, linux-3.13-1-686, mysql-5.5.35
2xPII 400, 768Mb RAM, 3x 9.3 Gb HDD
Все это было для заббикса 1.8.2 который там работал более года.
Что было сделано: для проверки винт, с разделом /var был скопирован на другой и заменен. На новом винте проапгрейдил заббикс до 2.2.2, последовательно конвертил базу 1.8->2.0-2.2 - все прошло нормально. Какое-то время все поработало После, снова вернул старый винт на место перекинув на него инфу с нового. Права были правильные, до копирования все сервисы остановил. И после...
140403 14:51:35 [Note] Plugin 'FEDERATED' is disabled.
140403 14:51:35 InnoDB: The InnoDB memory heap is disabled
140403 14:51:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140403 14:51:35 InnoDB: Compressed tables use zlib 1.2.8
140403 14:51:35 InnoDB: Using Linux native AIO
140403 14:51:35 InnoDB: Initializing buffer pool, size = 128.0M
140403 14:51:35 InnoDB: Completed initialization of buffer pool
140403 14:51:35 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 134631138646
140403 14:51:35 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 134631139426
140403 14:51:36 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 9 10 11 12 13 14 15 16 11:51:36 UTC - 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=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=50
thread_count=0
connection_count=0
It is possible that mysqld could use up to.
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 125553 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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...
stack_bottom = 0 thread_stack 0x30000
Что было испробовано:
- Память, винт, железо тестил - все ОК.
- Права на /var/lib/mysql везде mysql:mysql
- Запускал myisamchk --silent --force */*.MYI - ничего не сделало
- mysqld --skip-external-locking сегфолтится.
- Выставлял различные размеры кэша, запросов, таймауты - бестолку.
База повреждена, говорит, но как ее пофиксить?
my.cnf
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
bind-address = 127.0.0.1
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
myisam-recover = BACKUP
query_cache_limit = 1M
query_cache_size = 16M
log_error = /var/log/mysql/error.log
expire_logs_days = 10
max_binlog_size = 100M
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
[isamchk]
key_buffer = 16M
!includedir /etc/mysql/conf.d/
