Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.5
-
Fix Version/s: N/A
-
Component/s: Storage Engine - InnoDB
-
Labels:None
-
Environment:Windows Server 2008R2
MariaDB 5.5.28a
Description
Random crash
Logs:
InnoDB: Assertion failure in thread 2824 in file buf0buf.c line 2549 InnoDB: Failing assertion: block_mutex
—
my.cnf
[mysqld] datadir=C:/Program Files/MariaDB 5.5/data port=3306 sql_mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION" default_storage_engine=innodb innodb_buffer_pool_size = 12G innodb_additional_mem_pool_size = 16M innodb_log_file_size = 300M character-set-server=utf8 collation-server = utf8_bin skip-name-resolve query_cache_size=8388608 query_cache_limit=64M thread_cache_size=256 read_rnd_buffer_size = 16M innodb_write_io_threads = 8 innodb_read_io_threads = 8 innodb_flush_log_at_trx_commit = 2 max_allowed_packet=500M innodb_file_per_table=1 max_connections = 500 innodb_fast_shutdown = 2 innodb_file_format = Barracuda
—
Windows Event Log^
Faulting application name: mysqld.exe, version: 5.5.28.3587, time stamp: 0x50b6383f Faulting module name: mysqld.exe, version: 5.5.28.3587, time stamp: 0x50b6383f Exception code: 0x80000003 Fault offset: 0x000000000030e128 Faulting process id: 0x5e0 Faulting application start time: 0x01d06d3f6c3a3111 Faulting application path: c:\Program Files\MariaDB 5.5\bin\mysqld.exe Faulting module path: c:\Program Files\MariaDB 5.5\bin\mysqld.exe Report Id: f60e492a-e340-11e4-adb9-00155dbf3912
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Ok, i'll upgrade soon. And yes, we have the same MDEV-701 issue too. Thank you!
I will close it for now as fixed (with MDEV-701), but please comment if you keep experiencing any of these problems after upgrading, and the report will be re-opened.
Hi,
5.5.28 version is 2.5 years old, since then there have been lots of bugfixes in XtraDB/InnoDB. Just to mention one, there was
MDEV-701/ LP:905334 around the same area and could very well be related, fixed in the very next 5.5.29 version.I suggest to consider upgrading, especially if you keep getting this random crash. The current 5.5 release is 5.5.42, and 5.5.43 is coming soon.