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

"Unexpected internal state: received response 0x00 from server" after upgrade from from 2.3.4 to 2.3.17

Details

    • MXS-SPRINT-113

    Description

      After an upgrade from MaxScale 2.3.4 to 2.3.17, the maxscale log shows entries of the form

      2020-04-08 19:33:41 error : (30245) Unexpected internal state: received response 0x00 from server 'server1' when no response was expected. Command: 0x03 Query: <not available>

      every once in a while.

      Attachments

        Activity

          markus makela markus makela added a comment -

          Knowing how to reproduce this would help. Adding retain_last_statements=100 and dump_last_statements=on_error would show the previous SQL executed before the error is logged.

          markus makela markus makela added a comment - Knowing how to reproduce this would help. Adding retain_last_statements=100 and dump_last_statements=on_error would show the previous SQL executed before the error is logged.
          markus makela markus makela added a comment -

          Added some extra logging to the next 2.3 release that'll show the latest session command whenever one of these messages is logged. That in addition to retain_last_statements=100 should help reveal what is going on.

          markus makela markus makela added a comment - Added some extra logging to the next 2.3 release that'll show the latest session command whenever one of these messages is logged. That in addition to retain_last_statements=100 should help reveal what is going on.

          People

            markus makela markus makela
            hholzgra Hartmut Holzgraefe
            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.