[MDEV-13910] after update not starting Created: 2017-09-26  Updated: 2017-09-26  Resolved: 2017-09-26

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.1.27
Fix Version/s: 10.1.28

Type: Bug Priority: Major
Reporter: Thorsten Dworak Assignee: Andrii Nikitin (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Ubuntu 16.04.3 LTS


Issue Links:
Duplicate
is duplicated by MDEV-13787 Crash in persistent stats wsrep_on (t... Closed
is duplicated by MDEV-13908 10.1.27 Segfaulting Closed

 Description   

Description: Ubuntu 16.04.3 LTS
Kernel: linux-image-4.11.0-14-generic
Repo: mariadb.org/repo/10.1/ubuntu xenial main

mysql-error-log

...
2017-09-26 10:20:44 140474915764480 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.27-MariaDB-1~xenial'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
170926 10:20:44 [ERROR] 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.
 
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.27-MariaDB-1~xenial
key_buffer_size=1073741824
read_buffer_size=2097152
max_used_connections=0
max_threads=4002
thread_count=65
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17523288 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x47f8b5e4ae]
/usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x47f86a7025]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fc2dbde6390]
/usr/sbin/mysqld(wsrep_on+0x18)[0x47f8640ea8]
/usr/sbin/mysqld(+0x8f2336)[0x47f89f9336]
/usr/sbin/mysqld(+0x8f329f)[0x47f89fa29f]
/usr/sbin/mysqld(+0x8aa088)[0x47f89b1088]
/usr/sbin/mysqld(+0x8aa822)[0x47f89b1822]
/usr/sbin/mysqld(+0x9bacf7)[0x47f8ac1cf7]
/usr/sbin/mysqld(+0x9bbe17)[0x47f8ac2e17]
/usr/sbin/mysqld(+0x9be18b)[0x47f8ac518b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fc2dbddc6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc2db4873dd]
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.

syslog

kernel: [3718092.486033] mysqld[32696]: segfault at 950 ip 000000d64918fea8 sp 00007f1a43ff9830 error 4 in mysqld[d648c56000+f0b000]

other Kernel ( linux-image-4.10.0-35-generic ) the same

kernel: [   34.915202] mysqld[3700]: segfault at 950 ip 00005650bbc7fea8 sp 00007f4191bf9830 error 4 in mysqld[5650bb746000+f0b000]



 Comments   
Comment by Thorsten Dworak [ 2017-09-26 ]

I downgrade to V10.1.26 and the service is starting

aptitude install mariadb-server-10.1=10.1.26+maria-1~xenial
aptitude install mariadb-server-core-10.1=10.1.26+maria-1~xenial
aptitude install mysql-common=10.1.26+maria-1~xenial

Comment by Andrii Nikitin (Inactive) [ 2017-09-26 ]

This is very likely duplicate of MDEV-13787 . Yes it is better to stay on 10.1.26 until fix is released or try workaround innodb_stats_persistent=0

Comment by Sergei Golubchik [ 2017-09-26 ]

This is probably a duplicate of MDEV-13908

Generated at Thu Feb 08 08:09:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.