mysql - Yum updating Percona from 5.6.25-rel73.1 to 5.6.26-rel74.0 results in an unstartable server -


running under centos 6.7 yum updating percona server leaves in unstartable state.

this log /var/log/mysqld.log

150929 14:54:17 mysqld_safe starting mysqld daemon databases /srv/mysql 2015-09-29 14:54:18 0 [warning] timestamp implicit default value deprecated. please use --explicit_defaults_for_timestamp server option (see documentation more details). 2015-09-29 14:54:18 0 [note] /usr/sbin/mysqld (mysqld 5.6.26-74.0) starting process 17130 ... 2015-09-29 14:54:18 17130 [note] plugin 'federated' disabled. 2015-09-29 14:54:18 17130 [note] innodb: using atomics ref count buffer pool pages 2015-09-29 14:54:18 17130 [note] innodb: innodb memory heap disabled 2015-09-29 14:54:18 17130 [note] innodb: mutexes , rw_locks use gcc atomic builtins 2015-09-29 14:54:18 17130 [note] innodb: memory barrier 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 barracuda. 2015-09-29 14:54:18 17130 [error] innodb: tried read 4096 bytes @ offset 286720. able read 0. 2015-09-29 14:54:18 7fe0f5f847e0  innodb: operating system error number 22 in file operation. innodb: error number 22 means 'invalid argument'. innodb: operating system error numbers described @ 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 pid file /var/run/mysqld/mysqld.pid ended 

the my.cnf looks this:

[mysqld] socket=/var/lib/mysql/mysql.sock user=mysql # disabling symbolic-links recommended 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 bulk inserts 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 

the culprit seems line:

innodb_track_changed_pages = true

in order work around this...

  1. we changed innodb_track_changed_pages false
  2. stop server
  3. manually delete ib_modified_log* files in mysql directory
  4. start server
  5. change innodb_track_changed_pages true
  6. restart server

this seems bug.


Comments

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -