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

Maxscale Segfault on get_password

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 2.4.17
    • N/A
    • None
    • None
    • Kubernetes using official maxscale images

    Description

      Looks like we received a segfault today on a running instance.

       
      2022-05-02 17:15:23.580   warning: (5975581) (change_rlag_state): Replication lag of 'replica0' is 0s, which is below the configured limit 30s. 'replica0' is returned to query routing.
      2022-05-02 17:15:23.580   warning: (5975581) (change_rlag_state): Replication lag of 'replica1' is 0s, which is below the configured limit 30s. 'replica1' is returned to query routing.
      Fatal: MaxScale 2.4.17 received fatal signal 11. Commit ID: a8bfbbe254095d931aed351871fee72ce9ea645c System name: Linux Release string: CentOS Linux release 8.3.2011
       
      2022-05-03 15:01:45.271   alert  : (6526982) (sigfatal_handler): Fatal: MaxScale 2.4.17 received fatal signal 11. Commit ID: a8bfbbe254095d931aed351871fee72ce9ea645c System name: Linux Release string: CentOS Linux release 8.3.2011
      2022-05-03 15:01:45.271   alert  : (6526982) (sigfatal_handler): Statement currently being classified: none/unknown
      nm: /lib64/libsqlite3.so.0: no symbols
      2022-05-03 15:01:46.452   alert  : (6526982) (sigfatal_handler):
        /lib64/libsqlite3.so.0(sqlite3_exec+0x12a): ??:0
        /usr/lib64/maxscale/libmariadbauth.so.1.0.0(get_password+0x416): server/modules/authenticator/MariaDBAuth/dbusers.cc:448
        /usr/lib64/maxscale/libmariadbauth.so.1.0.0(validate_mysql_user+0x55): server/modules/authenticator/MariaDBAuth/dbusers.cc:468
        /usr/lib64/maxscale/libmariadbauth.so.1.0.0(+0x5d8b): server/modules/authenticator/MariaDBAuth/mysql_auth.cc:408
        /usr/lib64/maxscale/libmariadbclient.so(+0x6454): server/modules/protocol/MySQL/mariadbclient/mysql_client.cc:976
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0xa38cc): server/core/dcb.cc:2710
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0xa3b61): server/core/dcb.cc:2757
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x196): maxutils/maxbase/src/worker.cc:858
        /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x53): maxutils/maxbase/src/worker.cc:559
        /lib64/libstdc++.so.6(+0xc2ba3): ??:?
        /lib64/libpthread.so.0(+0x814a): pthread_create.c:?
        /lib64/libc.so.6(clone+0x43): :?
       
       
      Writing core dump
      

      Close as I could find was: https://jira.mariadb.org/browse/MXS-3585
      Is it possible the sqllite db for the users was corrupted?

      Attachments

        Activity

          People

            Unassigned Unassigned
            jsmelser_recharge Jeff Smelser
            Votes:
            0 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.