2015-09-29 1 views
0

Выполняется при обновлении CentOS версии 6.7 yum Server Percona оставляет его в нестабильном состоянии.Обновление Yum Percona от 5.6.25-rel73.1 до 5.6.26-rel74.0 приводит к неаргируемому серверу

Это из журнала /var/log/mysqld.log

150929 14:54:17 mysqld_safe Starting mysqld daemon with databases from /srv/mysql 
2015-09-29 14:54:18 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 
2015-09-29 14:54:18 0 [Note] /usr/sbin/mysqld (mysqld 5.6.26-74.0) starting as process 17130 ... 
2015-09-29 14:54:18 17130 [Note] Plugin 'FEDERATED' is disabled. 
2015-09-29 14:54:18 17130 [Note] InnoDB: Using atomics to ref count buffer pool pages 
2015-09-29 14:54:18 17130 [Note] InnoDB: The InnoDB memory heap is disabled 
2015-09-29 14:54:18 17130 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 
2015-09-29 14:54:18 17130 [Note] InnoDB: Memory barrier is not used 
2015-09-29 14:54:18 17130 [Note] InnoDB: Compressed tables use zlib 1.2.3 
2015-09-29 14:54:18 17130 [Note] InnoDB: Using Linux native AIO 
2015-09-29 14:54:18 17130 [Note] InnoDB: Using CPU crc32 instructions 
2015-09-29 14:54:18 17130 [Note] InnoDB: Initializing buffer pool, size = 3.0G 
2015-09-29 14:54:18 17130 [Note] InnoDB: Completed initialization of buffer pool 
2015-09-29 14:54:18 17130 [Note] InnoDB: Highest supported file format is Barracuda. 
2015-09-29 14:54:18 17130 [ERROR] InnoDB: Tried to read 4096 bytes at offset 286720. Was only able to read 0. 
2015-09-29 14:54:18 7fe0f5f847e0 InnoDB: Operating system error number 22 in a file operation. 
InnoDB: Error number 22 means 'Invalid argument'. 
InnoDB: Some operating system error numbers are described at 
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 
2015-09-29 14:54:18 17130 [ERROR] InnoDB: File (unknown): 'read' returned OS error 122. Cannot continue operation 
150929 14:54:18 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 

my.cnf выглядит примерно так:

[mysqld] 
socket=/var/lib/mysql/mysql.sock 
user=mysql 
# Disabling symbolic-links is recommended to prevent assorted security risks 
symbolic-links=0 
innodb_track_changed_pages = true 
pid-file=/var/run/mysqld/mysqld.pid 

# use interleaved id creation during bulk inserts 
# w/o this bulk inserts are serialized 
innodb_autoinc_lock_mode=2 

innodb_log_file_size = 2000M 
innodb_flush_method = O_DIRECT 
#innodb_buffer_pool_size = 80G 
innodb_buffer_pool_size = 5G 
transaction-isolation=READ-COMMITTED 

innodb_file_per_table=1 
default-storage-engine = InnoDB 
innodb_file_format = Barracuda 

Преступник, кажется, эта линия:

innodb_track_changed_pages = true

ответ

0

Чтобы обойти это ...

  1. Мы изменили innodb_track_changed_pages ложные
  2. Остановите сервер
  3. вручную удалить ib_modified_log* файлов в каталоге тузда
  4. Запустите сервер
  5. Изменения innodb_track_changed_pages истинного
  6. Перезапустите сервер

Кажется, что я это ошибка.

 Смежные вопросы

  • Нет связанных вопросов^_^