[MXS-877] RW Splitter Debug Assertion Hit Created: 2016-09-23  Updated: 2016-10-10  Resolved: 2016-10-10

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 2.0.1
Fix Version/s: 2.0.1

Type: Bug Priority: Major
Reporter: Kurt Pastore (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

CentOS Linux release 7.2.1511 (Core)



 Description   

2016-09-23 16:29:52 error : debug assert /home/vagrant/workspace/server/modules/routing/readwritesplit/readwritesplit.c:960
2016-09-23 16:29:52 error : Fatal: MaxScale 2.0.1 received fatal signal 6. Attempting backtrace.
2016-09-23 16:29:52 error : Commit ID: e618370cdbd56a05dfc1da7c89b90022018d170c System name: Linux Release string: NAME="CentOS Linux"
2016-09-23 16:29:52 error : /usr/bin/maxscale() [0x403f33]
2016-09-23 16:29:52 error : /lib64/libpthread.so.0(+0xf100) [0x7f9df08de100]
2016-09-23 16:29:52 error : /lib64/libc.so.6(gsignal+0x37) [0x7f9def2f85f7]
2016-09-23 16:29:52 error : /lib64/libc.so.6(abort+0x148) [0x7f9def2f9ce8]
2016-09-23 16:29:52 error : /lib64/libc.so.6(+0x2e566) [0x7f9def2f1566]
2016-09-23 16:29:52 error : /lib64/libc.so.6(+0x2e612) [0x7f9def2f1612]
2016-09-23 16:29:52 error : /usr/lib64/maxscale/libreadwritesplit.so(+0x3a70) [0x7f9deb157a70]
2016-09-23 16:29:52 error : /usr/lib64/maxscale/libMySQLClient.so(+0x473c) [0x7f9de99fb73c]
2016-09-23 16:29:52 error : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x340ce) [0x7f9df11f60ce]
2016-09-23 16:29:52 error : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x33d1a) [0x7f9df11f5d1a]
2016-09-23 16:29:52 error : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(dcb_process_zombies+0x2d4) [0x7f9df11f5b1e]
2016-09-23 16:29:52 error : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(poll_waitevents+0x719) [0x7f9df12148d3]
2016-09-23 16:29:52 error : /usr/bin/maxscale(worker_thread_main+0x2a) [0x4051d3]
2016-09-23 16:29:52 error : /lib64/libpthread.so.0(+0x7dc5) [0x7f9df08d6dc5]
2016-09-23 16:29:52 error : /lib64/libc.so.6(clone+0x6d) [0x7f9def3b928d]



 Comments   
Comment by markus makela [ 2016-09-24 ]

The crash happens when the state related to an active operation is not cleared when it should be. As a fail-safe, it could be cleared even when it shouldn't be there.

Comment by markus makela [ 2016-10-10 ]

Debug assertion fixed.

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