Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-31593

Constant aborted_clients due to read/write errors

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.12
    • None
    • None
    • None
    • Ubuntu 22

    Description

      [Warning] Aborted connection 253668 to db: 'xxx' user: 'xxx' host: 'localhost' (Got an error writing communication packets)
      [Warning] Aborted connection 255472 to db: 'xxx' user: 'xxx' host: 'localhost' (Got an error reading communication packets)

      I have done everything everything possible to resolve the issue including.

      Raising max allowed packets
      Raising php timeouts
      Raising mysql timeouts
      Disabling all wordpress plugins
      Reinstalling wordpress / checksumming wordpress
      Disabling redis
      Migrating to new server to ensure no hardware issues

      Mariadb is running locally to wordpress so there are no network issues. I can see the aborted_client count increasing every second in sync with these read/write errors. The error logs at max verbosity do not give enough information. I've looked at php error logs, open lite speed error logs, wordpress error logs, performance schema. No information is given as to why connections are being aborted.

      When I look at mariadb general access logs I can see the last query before the connection is aborted is always a simple select query.

      I have had several mariadb database admins look at the issue and everyones conclusion is that it is a bug.

      Attachments

        Activity

          There are no comments yet on this issue.

          People

            Unassigned Unassigned
            zddshp63 zddshp63
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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