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

MariaDB is not respecting log_warning (Windows)

Details

    Description

      My mariadb error log is reaching GB due to many notes I don't want it to log, I have tried all levels of log_warning especially 2 which should only show errors and none of the levels are respected.

      These notes are making my log reach GB and I need to delete it every day!

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          elenst Elena Stepanova added a comment -

          log_warnings=2 is the default value which does include some additional warnings. If there is a need to reduce the volume, the best shot would be log_warnings=0, but I don't see any indication that it would help with these particular ones.

          Assigning to marko for further consideration: if these messages can indeed be so frequent and are innocent (hence "notes"), surely they should be moved a level or two up.

          elenst Elena Stepanova added a comment - log_warnings=2 is the default value which does include some additional warnings. If there is a need to reduce the volume, the best shot would be log_warnings=0 , but I don't see any indication that it would help with these particular ones. Assigning to marko for further consideration: if these messages can indeed be so frequent and are innocent (hence "notes"), surely they should be moved a level or two up.
          marko Marko Mäkelä added a comment -

          Kevenny, can you explain the scenario in a little more detail? Do you know what could have been tablespace 4326453 that repeatedly occurs in log_error.png? If that tablespace still exists, it should be visible via INFORMATION_SCHEMA.INNODB_SYS_TABLES.SPACE or INFORMATION_SCHEMA.INNODB_SYS_TABLESPACES.

          marko Marko Mäkelä added a comment - Kevenny , can you explain the scenario in a little more detail? Do you know what could have been tablespace 4326453 that repeatedly occurs in log_error.png ? If that tablespace still exists, it should be visible via INFORMATION_SCHEMA.INNODB_SYS_TABLES.SPACE or INFORMATION_SCHEMA.INNODB_SYS_TABLESPACES .
          Kevenny Kevenny Ferraz de Lima added a comment - - edited

          Several schemas (dump) are restored in this Mariadb (centralized) and executed by an application, and more than one may be using the same schema.

          Notes I don't know why there are so many, but the problem is that it fills the log and I've already tried using log_warning=0 but it didn't solve it!

          The problem is only occurring on Windows as far as I checked!

          Kevenny Kevenny Ferraz de Lima added a comment - - edited Several schemas (dump) are restored in this Mariadb (centralized) and executed by an application, and more than one may be using the same schema. Notes I don't know why there are so many, but the problem is that it fills the log and I've already tried using log_warning=0 but it didn't solve it! The problem is only occurring on Windows as far as I checked!

          People

            marko Marko Mäkelä
            Kevenny Kevenny Ferraz de Lima
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.