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

[ERROR] Could not use for logging (error 2). fix the cause, shutdown the MariaDB server and restart it

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.5(EOL)
    • None
    • None
    • None
    • OS : RHEL 8.3 x86_64 4.18.0-240.22.1.el8_3.x86_64
      CPU : 8
      RAM : 32G

      Database : 10.5.9-MariaDB-log

    Description

      The error log message "Turning logging off for the whole duration of the MariaDB server process. To turn it on again: fix the cause, shutdown the MariaDB server and restart it." was noticed .

      The Encrypted Database has bin_log enabled , There is enough space available in bin log path. but "show master status" showing blank . when executed flush logs, the logs did not got created in log path. the error is getting logged in mariadb.

      The database has Master Slave replication. since the log is not getting created the sync got stopped.

      The issue got resolved after restarting the db services, these has caused down time for application for 10 min.

      Please help in understanding the issue and advise on solution.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              MurthyRamachandrula R S N Murthy
              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.