[MDEV-8208] Sporadic SEGFAULT on startup Created: 2015-05-22  Updated: 2016-05-09  Resolved: 2015-09-17

Status: Closed
Project: MariaDB Server
Component/s: wsrep
Affects Version/s: 5.5.43-galera, 10.0.19-galera
Fix Version/s: 5.5.46-galera, 10.0.22-galera

Type: Bug Priority: Major
Reporter: Nirbhay Choubey (Inactive) Assignee: Nirbhay Choubey (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-7915 wsrep.foreign_key, wsrep.pool_of_thre... Closed
Relates
relates to MDEV-10041 Server crashes sporadically during bo... Closed
Sprint: 10.1.7-2

 Description   

150513 16:16:09 [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 http://kb.askmonty.org/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: 5.5.43-MariaDB-1~precise-wsrep-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62548 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0x7f6a82412000
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 = 0x7f6a843fba30 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xaa187b]
/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x6edf78]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f6a8e60bcb0]
/usr/sbin/mysqld[0x9b370b]
/usr/sbin/mysqld(_Z15ha_commit_transP3THDb+0x266)[0x6f1106]
/usr/sbin/mysqld(_Z21ha_enable_transactionP3THDb+0x2f)[0x6f43bf]
/usr/sbin/mysqld(_ZN3THD16init_for_queriesEv+0x81)[0x57bca1]
/usr/sbin/mysqld(start_wsrep_THD+0x33a)[0x52775a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f6a8e603e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6a8cea24bd]



 Comments   
Comment by Nirbhay Choubey (Inactive) [ 2015-05-22 ]

http://lists.askmonty.org/pipermail/commits/2015-May/007941.html

Comment by Jan Lindström (Inactive) [ 2015-05-22 ]

Ok to push. I assume here that #ifdef WITH_WSREP is not necessary and we can't check if (WSREP_ON).

Comment by Nirbhay Choubey (Inactive) [ 2015-05-24 ]

jplindst WITH_WSREP is required as the affected code is part of wsrep-patch and check for WSREP_ON is not needed pre-10.1 as wsrep is always initialized on server start.

Comment by Nirbhay Choubey (Inactive) [ 2015-05-24 ]

https://github.com/MariaDB/server/commit/9eff9ed5c58e782abf383a52a7e691a55b4798a2

Comment by Nirbhay Choubey (Inactive) [ 2015-06-26 ]

10.0-galera is still affected.

Comment by Nirbhay Choubey (Inactive) [ 2015-07-07 ]

jplindst It another take on fixing this issue. Would you be interested in reviewing it?

http://lists.askmonty.org/pipermail/commits/2015-July/008150.html

Comment by Jan Lindström (Inactive) [ 2015-07-21 ]

See my comments on email.

Comment by Nirbhay Choubey (Inactive) [ 2015-08-20 ]

Recommitted the last patch with a better commit message:
http://lists.askmonty.org/pipermail/commits/2015-August/008269.html

Comment by Nirbhay Choubey (Inactive) [ 2015-09-15 ]

Responded to the review comments.

Comment by Nirbhay Choubey (Inactive) [ 2015-09-17 ]

https://github.com/MariaDB/server/commit/db2e21bf3ea32115e25bc6d9f67249042f16cadb

Comment by Elena Stepanova [ 2015-09-24 ]

nirbhay_c,
Can you merge the fix up to 10.1? It affects buildbot.

Comment by Nirbhay Choubey (Inactive) [ 2015-09-26 ]

Pushed to 10.1.

Generated at Thu Feb 08 07:25:26 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.