[MXS-2464] Crash in route_stored_query with ReadWriteSplit Created: 2019-05-02  Updated: 2020-08-25  Resolved: 2019-05-31

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 2.3.3, 2.3.4, 2.3.6, 2.3.7
Fix Version/s: 2.3.8

Type: Bug Priority: Critical
Reporter: Geoff Montee (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 3
Labels: None

Issue Links:
Relates
relates to MXS-2461 Unexpected internal state with ReadWr... Closed
Sprint: MXS-SPRINT-82, MXS-SPRINT-83

 Description   

A user is seeing the following crash in MaxScale 2.3.6:

2019-05-02 06:30:11 alert : (15297) Fatal: MaxScale 2.3.6 received fatal signal 11. Attempting backtrace.
2019-05-02 06:30:11 alert : (15297) Commit ID: 03dc969cf203decb4d0bc65280fe4f901da87830 System name: Linux Release string: NAME="CentOS Linux"
2019-05-02 06:30:11 alert : (15297) /usr/bin/maxscale(_ZN7maxbase15dump_stacktraceESt8functionIFvPKcS2_EE+0x2b) [0x40cbab]: /home/vagrant/MaxScal
e/maxutils/maxbase/src/stacktrace.cc:130
2019-05-02 06:30:11 alert : (15297) /usr/bin/maxscale(_ZN7maxbase15dump_stacktraceEPFvPKcS1_E+0x4e) [0x40cf0e]: /usr/include/c++/4.8.2/functional
:2029
2019-05-02 06:30:11 alert : (15297) /usr/bin/maxscale() [0x4095b9]: ??:0
2019-05-02 06:30:11 alert : (15297) /lib64/libpthread.so.0(+0xf6d0) [0x7f7767a6b6d0]: sigaction.c:?
2019-05-02 06:30:11 alert : (15297) /usr/lib64/maxscale/libreadwritesplit.so(_ZN14RWSplitSession18route_stored_queryEv+0x1f9) [0x7f775f54b949]: /
home/vagrant/MaxScale/include/maxscale/protocol/mysql.h:633
2019-05-02 06:30:11 alert : (15297) /usr/lib64/maxscale/libreadwritesplit.so(_ZN14RWSplitSession11clientReplyEP5gwbufP3dcb+0x3be) [0x7f775f54d6ee
]: /home/vagrant/MaxScale/server/modules/routing/readwritesplit/rwsplitsession.cc:752
2019-05-02 06:30:11 alert : (15297) /usr/lib64/maxscale/libreadwritesplit.so(_ZN8maxscale6RouterI7RWSplit14RWSplitSessionE11clientReplyEP10mxs_ro
uterP18mxs_router_sessionP5gwbufP3dcb+0x24) [0x7f775f5479e4]: /home/vagrant/MaxScale/include/maxscale/router.hh:206
2019-05-02 06:30:11 alert : (15297) /usr/lib64/maxscale/libmariadbbackend.so(+0x43a7) [0x7f775fd8d3a7]: /home/vagrant/MaxScale/server/modules/pro
tocol/MySQL/mariadbbackend/mysql_backend.cc:1041
2019-05-02 06:30:11 alert : (15297) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x7cbc7) [0x7f7768197bc7]: /home/vagrant/MaxScale/server/cor
e/dcb.cc:3136
2019-05-02 06:30:11 alert : (15297) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x7cd61) [0x7f7768197d61]: /home/vagrant/MaxScale/server/cor
e/dcb.cc:3228
2019-05-02 06:30:11 alert : (15297) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x1b5) [0x7f77681f3ae5]
: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:844
2019-05-02 06:30:11 alert : (15297) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x51) [0x7f77681f3ce1]
: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:545
2019-05-02 06:30:11 alert : (15297) /lib64/libstdc++.so.6(+0xb5070) [0x7f7766a9f070]: ??:?
2019-05-02 06:30:11 alert : (15297) /lib64/libpthread.so.0(+0x7e25) [0x7f7767a63e25]: pthread_create.c:?
2019-05-02 06:30:11 alert : (15297) /lib64/libc.so.6(clone+0x6d) [0x7f7765a44bad]: ??:?

This is the same user who was affected by MXS-2461 in MaxScale 2.3.4.



 Comments   
Comment by Valerii Kravchuk [ 2019-05-16 ]

It seems same crash happens even with proxy_protocol=false,

Comment by markus makela [ 2019-05-29 ]

2.3.8 will have some extra code that checks a few unexpected cases. If they were to happen we will have more information about why this happens.

Comment by markus makela [ 2019-05-31 ]

Managed to reproduce this locally.

Comment by Thomas J. Girsch [ 2019-05-31 ]

FYI, have also seen this in 2.3.7

Generated at Thu Feb 08 04:14:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.