MySQL Bugs: #74148: mysql crashes with writing error message into logbin.index

Bug #74148	mysql crashes with writing error message into logbin.index
Submitted:	30 Sep 2014 6:29	Modified:	7 Nov 2014 12:32
Reporter:	Zhenye Xie (OCA)	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.5.32	OS:	Linux (x86_64)
Assigned to:		CPU Architecture:	Any

Description:
mysql crashes with writing error message into logbin.index
it seems there is something wrong with 'flush logs'

error message in logbin.index:(last lines)
...
/data/dbaas/dtmngipt01dbBIN/log-bin.033129
/data/dbaas/dtmngipt01dbBIN/log-bin.033130
/data/dbaas/dtmngipt01dbBIN/log-bin.033131
/data/dbaas/dtmngipt01dbBIN/log-bin.033132
/data/dbaas/dtmngipt01dbBIN/log-bin.033133
/data/dbaas/dtmngipt01dbBIN/log-bin.033134
/data/dbaas/dtmngipt01dbBIN/log-bin.033135
/data/dbaas/dtmngipt01dbBIN/log-bin.033136
16:30:01 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=8388608
read_buffer_size=131072
max_used_connections=6
max_threads=2000
thread_count=3
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4383098 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fe43c0008b0
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 = 7fe56a53ce88 thread_stack 0x40000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (f6c270): flush logs
Connection ID (thread ID): 5001199
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

error message in error log:
/opt/dbaas/mysql-5.5/bin/mysqld(my_print_stacktrace+0x35)[0x7a2825]
/opt/dbaas/mysql-5.5/bin/mysqld(handle_fatal_signal+0x403)[0x670b43]
/lib64/libpthread.so.0(+0xf7c0)[0x7fe56a2a87c0]
[0x7fe44400b330]

my.cnf:
[mysqld]
bind-address=0.0.0.0
skip-name-resolve=1
symbolic-links=0
binlog_format=mixed
sync_binlog=1

replicate_ignore_db=mysql
replicate_wild_ignore_table=mysql.%
binlog_ignore_db=mysql

character_set_server=utf8

connect_timeout=60
interactive_timeout=31536000
wait_timeout=31536000

join_buffer_size = 128M
sort_buffer_size = 2M
read_rnd_buffer_size = 2M

table_open_cache=1000
table_definition_cache=1000
innodb_open_files=1000

innodb_autoinc_lock_mode = 2
innodb_log_file_size=256M
innodb_log_files_in_group=4

innodb_flush_method=O_DIRECT
innodb_max_dirty_pages_pct=30
innodb_additional_mem_pool_size=16M
innodb_lock_wait_timeout=60
innodb_rollback_on_timeout=on
innodb_file_per_table=on
innodb_stats_sample_pages=1
innodb_purge_threads=1
innodb_stats_on_metadata=off

slow_query_log=on
long_query_time=5
log_output=TABLE

max_user_connections=500
max_connections=2000
lower_case_table_names=1

How to repeat:
don't known how to repeat.

If you think that this is a problem with FLUSH LOGS, it is interesting IMO that you have "log_output=TABLE" defined for the slow query log.

Just an observation.

-- Peter
-- not a MySQL/Oracle person.

Please try version 5.5.40. Thanks.

Since it's product envionment and I cannot upgrade it unless the problem is confirmed fixed in the new version.

I don't see how binlogging is enabled in the my.cnf?
Also interesting to note a crash happened with only 3 connections...

some options are spicified by mysql arguments. such as logbin datadir

Thank you for the feedback. You have not provide a test case to repeat so you can try in test box since you have the elements to run a test. The instructions to report a bug is clear about to try the latest release. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".