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

MaxScale 22.08.3 received fatal signal 11

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • 22.08.3
    • N/A
    • kafkacdc
    • centos7.9 , 8cpu, 32gb ram, mariadb 10.3 with AES encryption enabled, maxscale 22.8.3
      [mariadb]
      file_key_management_encryption_algorithm=AES_CTR
    • MXS-SPRINT-175, MXS-SPRINT-176, MXS-SPRINT-177, MXS-SPRINT-190

    Description

      maxscale.cnf configuration

      # # The MariaDB-to-Kafka CDC service
      [Kafka-CDC]
      type=service
      router=kafkacdc
      servers=server1
      user=user
      password=password
      bootstrap_servers=backup-db-server:9092
      topic=test-cdc-topic
      gtid=0-1-32177538
      

      We are getting this error and messages are not sent accross to Kafka Server
      — Error

      2023-01-10 08:53:42   alert  : MaxScale 22.08.3 received fatal signal 11. Commit ID: 2949f820a7d9de38d7fd51909f66d561627d1eed System name: Linux Release string: NAME="CentOS Linux"
      2023-01-10 08:53:42   alert  : Statement currently being classified: none/unknown
      2023-01-10 08:53:42   notice : For a more detailed stacktrace, install GDB and add 'debug=gdb-stacktrace' under the [maxscale] section.
        /usr/lib64/maxscale/libreplicator.so.1.0.0(ZN3Rpl22process_row_event_dataERK5TablePhS3_S3+0x1006): ??:?
        /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3Rpl16handle_row_eventEP10REP_HEADERPh+0x4be): ??:?
        /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3Rpl12handle_eventE10REP_HEADERPh+0x67): ??:?
        /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3cdc10Replicator3Imp17process_one_eventERSt10unique_ptrI20st_mariadb_rpl_eventSt8functionIFvPS3_EEE+0xdd): ??:?
        /usr/lib64/maxscale/libreplicator.so.1.0.0(_ZN3cdc10Replicator3Imp14process_eventsEv+0x140): ??:?
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x4096d0): thread48.o:?
        /lib64/libpthread.so.0(+0x7ea5): pthread_create.c:?
        /lib64/libc.so.6(clone+0x6d): ??:?
      alert  : Writing core dump.
      

      Attachments

        Activity

          markus makela markus makela added a comment -

          Yes, that's what you'll need to do.

          markus makela markus makela added a comment - Yes, that's what you'll need to do.
          jayantworld@gmail.com Jayant Patil added a comment -

          Hi markus,

          It is still same error even changing the properties.

          jayantworld@gmail.com Jayant Patil added a comment - Hi markus, It is still same error even changing the properties.
          markus makela markus makela added a comment -

          Have you managed to reproduce this outside of your production environment?

          markus makela markus makela added a comment - Have you managed to reproduce this outside of your production environment?
          markus makela markus makela added a comment - - edited

          It might be that this commit fixed the problem. This was included in a recent release so you should be able to uprgade to it and test and see if it solves the problem.

          markus makela markus makela added a comment - - edited It might be that this commit fixed the problem. This was included in a recent release so you should be able to uprgade to it and test and see if it solves the problem.
          markus makela markus makela added a comment -

          I'll close this as Done based on the fact that the problem appeared in the same function that the aforementioned commit fixes. If you can reproduce this with the latest release of 22.08, please let us know and we'll reopen this.

          markus makela markus makela added a comment - I'll close this as Done based on the fact that the problem appeared in the same function that the aforementioned commit fixes. If you can reproduce this with the latest release of 22.08, please let us know and we'll reopen this.

          People

            markus makela markus makela
            jayantworld@gmail.com Jayant Patil
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.