[MXS-3976] crash signall 11 with kafkacdc and enabled binlog router Created: 2022-02-02  Updated: 2022-07-20  Resolved: 2022-07-06

Status: Closed
Project: MariaDB MaxScale
Component/s: binlogrouter
Affects Version/s: 6.2.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Richard Stracke Assignee: markus makela
Resolution: Incomplete Votes: 1
Labels: None

Sprint: MXS-SPRINT-151

 Description   

2022-02-01 22:50:42   info   : Row Event for 'tablename' at 817951321
2022-02-01 22:50:42   info   : [0] VARCHAR: field: 360 bytes, data: 15 bytes
2022-02-01 22:50:42   info   : [1] VARCHAR: field: 570 bytes, data: 42 bytes
2022-02-01 22:50:42   info   : [2] VARCHAR: field: 570 bytes, data: 15 bytes
2022-02-01 22:50:42   info   : [3] VARCHAR: field: 570 bytes, data: 18 bytes
2022-02-01 22:50:42   info   : [4] VARCHAR: field: 570 bytes, data: 12 bytes
2022-02-01 22:50:42   info   : [5] NULL
2022-02-01 22:50:42   info   : [6] LONGLONG
2022-02-01 22:50:42   info   : [7] LONGLONG
2022-02-01 22:50:42   info   : [8] LONG
2022-02-01 22:50:42   info   : [9] VARCHAR: field: 48 bytes, data: 7 bytes
2022-02-01 22:50:42   info   : [10] VARCHAR: field: 24 bytes, data: 6 bytes
2022-02-01 22:50:42   info   : [11] LONGLONG
2022-02-01 22:50:42   info   : [12] LONGLONG
2022-02-01 22:50:42   info   : [13] NULL
2022-02-01 22:50:42   info   : [14] SHORT
2022-02-01 22:50:42   info   : [15] BLOB: field: 2 bytes, data: 564 bytes
 
 
 
alert  : MaxScale 6.2.1 received fatal signal 11. Commit ID: 384129e62d4af72509b6640542eb5ee277304f26 System name: Linux Release string: NAME="CentOS Linux"
 
 
2022-02-01 22:50:42   alert  : MaxScale 6.2.1 received fatal signal 11. Commit ID: 384129e62d4af72509b6640542eb5ee277304f26 System name: Linux Release string: NAME="CentOS Linux"
2022-02-01 22:50:42   alert  : Statement currently being classified: none/unknown
2022-02-01 22:50:42   notice : For a more detailed stacktrace, install GDB and add 'debug=gdb-stacktrace' under the [maxscale] section.
  /lib64/libc.so.6(+0x16f8c1): :?
  /usr/lib64/maxscale/libkafkacdc.so(+0x40884): server/modules/routing/kafkacdc/kafkacdc.cc:313
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3Rpl16handle_row_eventEP10REP_HEADERPh+0x3f9): server/modules/routing/replicator/rpl.cc:2025
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3Rpl12handle_eventE10REP_HEADERPh+0x67): server/modules/routing/replicator/rpl.cc:2159
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3cdc10Replicator3Imp17process_one_eventERSt10unique_ptrI20st_mariadb_rpl_eventSt8functionIFvPS3_EEE+0xc7): server/modules/routing/replicator/replicator.cc:522 (discriminator 4)
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3cdc10Replicator3Imp14process_eventsEv+0x128): server/modules/routing/replicator/replicator.cc:324
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x2dddff): thread48.o:?
  /lib64/libpthread.so.0(+0x7ea5): pthread_create.c:?
  /lib64/libc.so.6(clone+0x6d): ??:?
alert  : Writing core dump.

Crash not happened with disabled binlog router.



 Comments   
Comment by Naresh Chandra [ 2022-02-02 ]

If we enable the binlog filter then Maxscale is crashing. Without binlog filter then maxscale running fine.

[BinlogFilter]
type=filter
module=binlogfilter
match=/customers[.]/
exclude=/[.]orders/

Comment by markus makela [ 2022-02-15 ]

This could be related to MXS-4000 but it still shouldn't cause a crash, just unwanted events being replicated.

Comment by Naresh Chandra [ 2022-02-15 ]

Hi Markus,

Without binlog filter only the binlog router working fine but when we enable binlog filter with binlog router then maxscale is crashing.

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