Your message dated Tue, 09 May 2017 17:50:09 +0000
with message-id <[email protected]>
and subject line Bug#862103: fixed in mariadb-10.1 10.1.23-6
has caused the Debian Bug report #862103,
regarding mariadb-server-10.1: MariaDB crash after throwing an instance of
'std::out_of_range'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
862103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862103
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mariadb-server-10.1
Version: 10.1.22-3
Severity: grave
Tags: newcomer upstream
Justification: causes non-serious data loss
Dear Maintainer,
A critical MySQL bug was discovered in InnoDB storage engine (related to
statistics calculation) some weeks ago.
This bug affects MariaDB 10.1 as well and is present in the current Debian
Stretch (MariaDB 10.1.22) package
[mariadb Ver 15.1 Distrib 10.1.22-MariaDB, for debian-linux-gnu (x86_64) using
readline 5.2].
Seems to also affect the unstable 10.1.23-3 package.
MariaDB crash very often on many of our server, from many times daily to many
times hourly.
The bug (and fix) is well described here :
https://bugs.mysql.com/bug.php?id=84940 (rated serious)
and here
https://jira.mariadb.org/browse/MDEV-12281 (rated critical)
The bug come from a missing bracket in the InnoDB Stats code and a patch is
available here :
https://github.com/mysql/mysql-server/commit/0241e1c1b216d87050cdfcb4531ffc17f9eb1dc7
Data corruption in InnoDB tables may occur as a side effect.
Typical Error/crash log :
-------------------------------------------------------------------------------------------
Version: '10.1.22-MariaDB-' socket: '/var/run/mysqld/mysqld.sock' port: 3306
Debian 9.0
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is 4294967295) >= this->size()
(which is 0)
170508 13:55:21 [ERROR] mysqld got signal 6 ;
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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
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.
Server version: 10.1.22-MariaDB-
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=5
max_threads=386
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 864227 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 = 0x0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5607ce9d50ce]
/usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x5607ce51e50d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7feadffc90c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7feade8c4fcf]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7feade8c63fa]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x15d)[0x7feadefc50ad]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8f066)[0x7feadefc3066]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8f0b1)[0x7feadefc30b1]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8f2c9)[0x7feadefc32c9]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt24__throw_out_of_range_fmtPKcz+0xf5)[0x7feadefebb85]
/usr/sbin/mysqld(+0x9ace97)[0x5607ce931e97]
/usr/sbin/mysqld(+0x9b07f4)[0x5607ce9357f4]
/usr/sbin/mysqld(+0x9b4626)[0x5607ce939626]
/usr/sbin/mysqld(+0x9b5d19)[0x5607ce93ad19]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7feadffbf494]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7feade97a93f]
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.
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Using mutexes to ref count
buffer pool pages
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: The InnoDB memory heap is
disabled
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Mutexes and rw_locks use GCC
atomic builtins
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: GCC builtin
__atomic_thread_fence() is used for memory barrier
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Compressed tables use zlib
1.2.8
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Using Linux native AIO
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Using SSE crc32 instructions
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Initializing buffer pool,
size = 2.0G
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Completed initialization of
buffer pool
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Highest supported file
format is Barracuda.
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Starting crash recovery from
checkpoint LSN=195680453668
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Restoring possible
half-written data pages from the doublewrite buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 100954368
2017-05-08 13:55:27 140012981801536 [Note] InnoDB: Starting final batch to
recover 107 pages from redo log
2017-05-08 13:55:28 140012981801536 [Note] InnoDB: 128 rollback segment(s) are
active.
InnoDB: Starting in background the rollback of uncommitted transactions
2017-05-08 13:55:28 7f56ab3fe700 InnoDB: Rolling back trx with id 100953855, 1
rows to undo
2017-05-08 13:55:28 140012981801536 [Note] InnoDB: Waiting for purge to start
2017-05-08 13:55:28 140010217006848 [Note] InnoDB: Rollback of trx with id
100953855 completed
2017-05-08 13:55:28 7f56ab3fe700 InnoDB: Rollback of non-prepared transactions
completed
2017-05-08 13:55:28 140012981801536 [Note] InnoDB: Percona XtraDB
(http://www.percona.com) 5.6.35-80.0 started; log sequence number 195733664191
2017-05-08 13:55:28 140012981801536 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-08 13:55:28 140010124715776 [Note] InnoDB: Dumping buffer pool(s) not
yet started
2017-05-08 13:55:28 140012981801536 [Note] Recovering after a crash using tc.log
2017-05-08 13:55:28 140012981801536 [Note] Starting crash recovery...
2017-05-08 13:55:28 140012981801536 [Note] Crash recovery finished.
2017-05-08 13:55:28 140012981801536 [Note] Server socket created on IP:
'127.0.0.1'.
2017-05-08 13:55:28 140012981801536 [Note] /usr/sbin/mysqld: ready for
connections.
-------------------------------------------------------------------------------------
It's my first bug report here, sorry if I miss something.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
(x86_64)
Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mariadb-server-10.1 depends on:
ii adduser 3.115
ii debconf [debconf-2.0] 1.5.60
ii galera-3 [galera-3] 25.3.20-stretch
ii gawk 1:4.1.4+dfsg-1
ii init-system-helpers 1.48
ii iproute2 4.9.0-1
ii libaio1 0.3.110-3
ii libc6 2.24-10
ii libdbi-perl 1.636-1+b1
ii libpam0g 1.1.8-3.5
ii libstdc++6 6.3.0-16
ii lsb-base 9.20161125
ii lsof 4.89+dfsg-0.1
ii mariadb-client-10.1 10.1.22-3
ii mariadb-common 10.1.23+maria-1~stretch
ii mariadb-server-core-10.1 10.1.22-3
ii passwd 1:4.4-4
ii perl 5.24.1-2
ii psmisc 22.21-2.1+b2
ii rsync 3.1.2-1
ii socat 1.7.3.1-2+b1
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages mariadb-server-10.1 recommends:
ii libhtml-template-perl 2.95-2
Versions of packages mariadb-server-10.1 suggests:
ii bsd-mailx [mailx] 8.1.2-0.20160123cvs-4
pn mariadb-test <none>
pn netcat-openbsd <none>
pn tinyca <none>
-- Configuration Files:
/etc/mysql/mariadb.conf.d/50-server.cnf changed:
[server]
[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_size = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
myisam_recover_options = BACKUP
max_connections = 384
query_cache_limit = 1M
query_cache_size = 16M
log_error = /var/log/mysql/error.log
slow_query_log = 1
slow_query_log_file = /var/log/mysql/mariadb-slow.log
long_query_time = 2
log_slow_rate_limit = 1000
log_slow_verbosity = query_plan
expire_logs_days = 10
max_binlog_size = 100M
innodb_buffer_pool_size = 2048M
character-set-server = utf8mb4
collation-server = utf8mb4_general_ci
[embedded]
[mariadb]
[mariadb-10.1]
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.23-6
We believe that the bug you reported is fixed in the latest version of
mariadb-10.1, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý <[email protected]> (supplier of updated mariadb-10.1 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 08 May 2017 19:51:47 +0200
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 10.1.23-6
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers <[email protected]>
Changed-By: Ondřej Surý <[email protected]>
Description:
libmariadbclient-dev - MariaDB database development files
libmariadbclient-dev-compat - MariaDB database development files
(libmysqlclient compatibility)
libmariadbclient18 - MariaDB database client library
libmariadbd-dev - MariaDB embedded database, development files
libmariadbd18 - MariaDB embedded database, shared library
mariadb-client - MariaDB database client (metapackage depending on the latest
vers
mariadb-client-10.1 - MariaDB database client binaries
mariadb-client-core-10.1 - MariaDB database core client binaries
mariadb-common - MariaDB common metapackage
mariadb-plugin-connect - Connect storage engine for MariaDB
mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin
for MariaDB
mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client
mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server
mariadb-plugin-mroonga - Mroonga storage engine for MariaDB
mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB
mariadb-plugin-spider - Spider storage engine for MariaDB
mariadb-plugin-tokudb - TokuDB storage engine for MariaDB
mariadb-server - MariaDB database server (metapackage depending on the latest
vers
mariadb-server-10.1 - MariaDB database server binaries
mariadb-server-core-10.1 - MariaDB database core server files
mariadb-test - MariaDB database regression test suite
mariadb-test-data - MariaDB database regression test suite - data files
Closes: 862103
Changes:
mariadb-10.1 (10.1.23-6) unstable; urgency=medium
.
* Also fix the same assertion failure in xtradb (Closes: #862103)
Checksums-Sha1:
3ae1ee42506389daccb4d20a70df103266a223c6 4384 mariadb-10.1_10.1.23-6.dsc
eb6fd4b725b41c668cd0fa36b6d25164e57d4d0c 221432
mariadb-10.1_10.1.23-6.debian.tar.xz
86dc2497e17e3d1824b84a20c8b814749794c0fb 19726
mariadb-10.1_10.1.23-6_amd64.buildinfo
Checksums-Sha256:
0ae98aced79f2b6be33ee6a1ed29be5bdf92c2c68eb2dd197a346e5008eb7e49 4384
mariadb-10.1_10.1.23-6.dsc
c49d1c6cb284f64e6869a2685c6c480daa8392e72770fbc7caf4f68c6c104a23 221432
mariadb-10.1_10.1.23-6.debian.tar.xz
7c8ae55fb7f16fd6f1997665302264175100151ec8baa55711500d3be61f8f27 19726
mariadb-10.1_10.1.23-6_amd64.buildinfo
Files:
f3175a0cd50e5ca4406209c83270cfce 4384 database optional
mariadb-10.1_10.1.23-6.dsc
4c5d54569c0152a3b5941a04ed997ea7 221432 database optional
mariadb-10.1_10.1.23-6.debian.tar.xz
84d0b20b216fc615fd69bd9cae62b547 19726 database optional
mariadb-10.1_10.1.23-6_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEEMLkz2A/OPZgaLTj7DJm3DvT8uwcFAlkQuu9fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDMw
QjkzM0Q4MEZDRTNEOTgxQTJEMzhGQjBDOTlCNzBFRjRGQ0JCMDcACgkQDJm3DvT8
uwfpDQ//e6rR9dkyriBIKvrDnnk0cghull4BRnwB8sTJttoaksbJcR+V68XzsNr5
NkecGmsRXoMAAduL2H+aXA/vEzuLBPqJHx5Y2zvMjONE0ZQumkWzM6V2MmldsxKQ
h7WcKNM3nxmkhgw0av5eofRwvDUntLRMNhUZbsp3tRMI7XQD61mUJxv03E83Q8VO
PEPzvrPEqsxg71rvoMkwy1AjsFpg6X2KIrg0xri5k/qqMWu+vfawdpkhB22z3h1Q
e1ngc9V+zkkvdWlswVc0Prs1ySQpP6RjKU6Zx2Kln0x54XjeWkDxUi4CiqEXcgWK
ouk4dQM7vLcI3ZpEbilfKg5tt6J/1KMQG2B9BbeQD1dONb1NVjxgV9FZVhJgC3D5
CeLPbxtwQWFoCPTVOvhgqY1cMm66rD/73hTtEabdWzsKoLoJgdsUHgWRTr9VB/1W
NhzoGuxhx5WYN7LCmxQfBXNKoh5NJrkOHl5BlWQIbh+0C+ehohlVO4nrlD/RWsRd
qjiq9OKpH9t/w+gRQqQ5O03x/yIGmHEsFlfqlF99WfmL2himFNWaPRCsPplXtBnb
O92CtEAmqkOmUOzfQCmDoJP0VGs0jDo089s/Bw3jBHEuWXZdO8HM82nmzI+SAVoa
UxMzVU2SaRi1R/JMH3J7DEOhIC/y0sGs1DIY6KF9yB3zRYP4ay8=
=5dlg
-----END PGP SIGNATURE-----
--- End Message ---
