Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3976

crash signall 11 with kafkacdc and enabled binlog router

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 6.2.1
    • N/A
    • binlogrouter
    • None
    • 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.

      Attachments

        Activity

          People

            markus makela markus makela
            Richard Richard Stracke
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.