[MXS-4674] Crash in mxs1687_avro_ha Created: 2023-07-19  Updated: 2023-08-15  Resolved: 2023-08-15

Status: Closed
Project: MariaDB MaxScale
Component/s: avrorouter
Affects Version/s: 23.02.2
Fix Version/s: 23.02.4

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-187, MXS-SPRINT-188

 Description   

MaxScale 23.02.3 received fatal signal 11. Commit ID: 2752b88a7d0037698da500c5f008464ffa704b15, System name: Linux, Release string: NAME="Rocky Linux", Thread: Replicator
 
2023-08-04 13:24:33   alert  : MaxScale 23.02.3 received fatal signal 11. Commit ID: 2752b88a7d0037698da500c5f008464ffa704b15, System name: Linux, Release string: NAME="Rocky Linux", Thread: Replicator
2023-08-04 13:24:33   alert  : Statement currently being classified: none/unknown
2023-08-04 13:24:33   notice : For a more detailed stacktrace, install GDB and add 'debug=gdb-stacktrace' under the [maxscale] section.
  /lib64/libpthread.so.0(+0x12cf0): ??:?
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3Rpl22handle_table_map_eventEP10REP_HEADERPh+0x311): server/modules/routing/replicator/rpl.cc:1896
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3Rpl12handle_eventE10REP_HEADERPh+0x327): server/modules/routing/replicator/rpl.cc:2221
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3cdc10Replicator3Imp17process_one_eventERSt10unique_ptrI20st_mariadb_rpl_eventSt8functionIFvPS3_EEE+0xce8): server/modules/routing/replicator/replicator.cc:552 (discriminator 4)
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3cdc10Replicator3Imp14process_eventsEv+0x505): server/modules/routing/replicator/replicator.cc:345
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZSt13__invoke_implIvMN3cdc10Replicator3ImpEFvvEPS2_JEET_St21__invoke_memfun_derefOT0_OT1_DpOT2_+0x159): /usr/include/c++/8/bits/invoke.h:73 (discriminator 4)
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZSt8__invokeIMN3cdc10Replicator3ImpEFvvEJPS2_EENSt15__invoke_resultIT_JDpT0_EE4typeEOS7_DpOS8_+0x37): /usr/include/c++/8/bits/invoke.h:96
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZNSt6thread8_InvokerISt5tupleIJMN3cdc10Replicator3ImpEFvvEPS4_EEE9_M_invokeIJLm0ELm1EEEEDTcl8__invokespcl10_S_declvalIXT_EEEEESt12_Index_tupleIJXspT_EEE+0x43): /usr/include/c++/8/thread:244
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZNSt6thread8_InvokerISt5tupleIJMN3cdc10Replicator3ImpEFvvEPS4_EEEclEv+0x18): /usr/include/c++/8/thread:253
  /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJMN3cdc10Replicator3ImpEFvvEPS5_EEEEE6_M_runEv+0x1c): /usr/include/c++/8/thread:196
  /lib64/libstdc++.so.6(+0xc2b13): ??:?
  /lib64/libpthread.so.0(+0x81ca): ??:?
  /lib64/libc.so.6(clone+0x43): :?
Writing core dump.



 Comments   
Comment by markus makela [ 2023-08-11 ]

This might be explained by CONC-659 if the offset into the replication event is off by two bytes. The sporadic nature of it definitely points towards this being the problem.

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