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

LP:802623 - general_log.CSV file not found causes replication to stop on server restart

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Trivial
        • Resolution: Incomplete
        • Affects Version/s: None
        • Fix Version/s: None
        • Component/s: None
        • Labels:

          Description

          Had to restart our MariaDB server today, and when I did, replication did not autostart back up because of two errors with general_log.CSV and slow_log.CSV. A bit of investigation showed that these files didn't exist in the /mysql/mysql/ dir, so i touched and chowned them to mysql:mysql. Then another start slave and all was fine.

          terminal output attached..

            Gliffy Diagrams

              Attachments

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                walterheck Walter Heck added a comment -

                general_log_bug.txt
                LPexportBug802623_general_log_bug.txt

                Show
                walterheck Walter Heck added a comment - general_log_bug.txt LPexportBug802623_general_log_bug.txt
                Hide
                Permalink
                walterheck Walter Heck added a comment -

                Re: general_log.CSV file not found causes replication to stop on server restart

                Show
                walterheck Walter Heck added a comment - Re: general_log.CSV file not found causes replication to stop on server restart
                Hide
                Permalink
                ratzpo Rasmus Johansson added a comment -

                Launchpad bug id: 802623

                Show
                ratzpo Rasmus Johansson added a comment - Launchpad bug id: 802623
                Hide
                Permalink
                elenst Elena Stepanova added a comment -

                Without knowing what made the file disappear in the first place, not much can be done. If the binlog has ALTER for a table and the table is not there, replication naturally fails.

                Show
                elenst Elena Stepanova added a comment - Without knowing what made the file disappear in the first place, not much can be done. If the binlog has ALTER for a table and the table is not there, replication naturally fails.

                  People

                  • Assignee:
                    knielsen Kristian Nielsen
                    Reporter:
                    walterheck Walter Heck
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: