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

Error log is too verbose

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • 2.0.0
    • Core
    • None

    Description

      Error log is really too verbose, resulting in hundreds of messages being written per second and flooding the error log, also causing IO spikes.

      For example let's take this error where maxscale reaches max connections, it will log an error for each connection error, in my humble opinion the rate of error write should be limited.

      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Splitter Service: Refresh rate limit exceeded for load of users' table.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Splitter Service: Refresh rate limit exceeded for load of users' table.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Splitter Service: Refresh rate limit exceeded for load of users' table.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Splitter Service: Refresh rate limit exceeded for load of users' table.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Invalid authentication message from backend. Error : 42000, Msg : User 'prddun' has exceeded the 'max_user_connections' resource (current value: 1000)
      2016-07-26 04:42:28 error : Splitter Service: Refresh rate limit exceeded for load of users' table.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.
      2016-07-26 04:42:28 error : Backend server didn't accept authentication for user prddun.

      Attachments

        Issue Links

          Activity

            People

              johan.wikman Johan Wikman
              tanj Guillaume Lefranc
              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.