Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-14509 Spider-VP Spiral Patches
  3. MDEV-14488

logging not happening on spider branch builds

Details

    Description

      I noticed that on startup of the binary that logging did not happen. This confused me.
      Looking further it turns out that the aria_log_control file is being written to instead which shouldn't happen.

      Ive tried to use this binary for some other spider tests after poking but it's still not working so think it's best to report this, fix it and then get a new binary.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14889 Server fails to start because of aria_log_control-file

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14337 mysqld_safe may suppress error messages with --log-output=file

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14714 mysqld writes status information on HUP signal into innodb data file, breaking it

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            sjmudd Simon Mudd added a comment -

            Note: also seen on a later build. rpm version is the same but the build date is newer:

            $ rpm -qi MariaDB-server-10.2.11
            		 
            Name        : MariaDB-server
            		 
            Version     : 10.2.11
            		 
            Release     : 1.el7.centos
            		 
            Architecture: x86_64
            		 
            Install Date: Thu 23 Nov 2017 12:30:59 PM CET
            		 
            Group       : Applications/Databases
            		 
            Size        : 479070812
            		 
            License     : GPLv2
            		 
            Signature   : (none)
            		 
            Source RPM  : MariaDB-server-10.2.11-1.el7.centos.src.rpm
            		 
            Build Date  : Thu 16 Nov 2017 05:10:05 PM CET
            		 
            Build Host  : centos70-x86-64
            		 
            Relocations : (not relocatable)
            		 
            Vendor      : MariaDB Foundation
            		 
            URL         : http://mariadb.org
            		 
            Summary     : MariaDB: a very fast and robust SQL database server

            The original failure was seen from the build-17004 but the same issue is seen on the 17169 directory.

            sjmudd Simon Mudd added a comment - Note: also seen on a later build. rpm version is the same but the build date is newer: $ rpm -qi MariaDB-server-10.2.11 Name : MariaDB-server Version : 10.2.11 Release : 1.el7.centos Architecture: x86_64 Install Date: Thu 23 Nov 2017 12:30:59 PM CET Group : Applications/Databases Size : 479070812 License : GPLv2 Signature : (none) Source RPM : MariaDB-server-10.2.11-1.el7.centos.src.rpm Build Date : Thu 16 Nov 2017 05:10:05 PM CET Build Host : centos70-x86-64 Relocations : (not relocatable) Vendor : MariaDB Foundation URL : http://mariadb.org Summary : MariaDB: a very fast and robust SQL database server The original failure was seen from the build-17004 but the same issue is seen on the 17169 directory.
            serg Sergei Golubchik added a comment -

            Fixed in MDEV-14337

            serg Sergei Golubchik added a comment - Fixed in MDEV-14337
            sjmudd Simon Mudd added a comment - - edited

            Note: This looks better. I see now:

            ....
            		 
            2017-12-13 10:41:20 0 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
            		 
            Version: '10.3.3-MariaDB-debug-log'  socket: 'mysql.sock'  port: 3306  Source distribution
            		 
            2017-12-13 10:41:31 0 [Note] Got signal 15 to shutdown mysqld
            		 
            2017-12-13 10:41:31 0 [Note] /usr/local/mysql/bin/mysqld (root[root] @ localhost []): Normal shutdown
            		 
             
            		 
            2017-12-13 10:41:31 0 [Note] InnoDB: FTS optimize thread exiting.
            		 
            2017-12-13 10:41:31 0 [Note] Event Scheduler: Killing the scheduler thread, thread id 26
            		 
            2017-12-13 10:41:31 0 [Note] Event Scheduler: Waiting for the scheduler thread to reply
            		 
            2017-12-13 10:41:31 0 [Note] Event Scheduler: Stopped
            		 
            2017-12-13 10:41:31 0 [Note] Event Scheduler: Purging the queue. 2 events
            		 
            2017-12-13 10:41:31 0 [Note] unregister_replicator OK
            		 
            2017-12-13 10:41:31 0 [Note] InnoDB: Starting shutdown...
            		 
            2017-12-13 10:41:31 0 [Note] InnoDB: Dumping buffer pool(s) to /mysql/xxxxx/data/ib_buffer_pool
            		 
            2017-12-13 10:41:31 0 [Note] InnoDB: Buffer pool(s) dump completed at 171213 10:41:31
            		 
            2017-12-13 10:41:32 0 [Note] InnoDB: Shutdown completed; log sequence number 133028285
            		 
            2017-12-13 10:41:32 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
            		 
            2017-12-13 10:41:32 0 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

            However, note the blank line that gets generated when the shutdown begins. it looks like there is an extra "\n" somewhere in the logging which should not be there. Perhaps this can be resolved too?

            sjmudd Simon Mudd added a comment - - edited Note: This looks better. I see now: .... 2017-12-13 10:41:20 0 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '10.3.3-MariaDB-debug-log' socket: 'mysql.sock' port: 3306 Source distribution 2017-12-13 10:41:31 0 [Note] Got signal 15 to shutdown mysqld 2017-12-13 10:41:31 0 [Note] /usr/local/mysql/bin/mysqld (root[root] @ localhost []): Normal shutdown   2017-12-13 10:41:31 0 [Note] InnoDB: FTS optimize thread exiting. 2017-12-13 10:41:31 0 [Note] Event Scheduler: Killing the scheduler thread, thread id 26 2017-12-13 10:41:31 0 [Note] Event Scheduler: Waiting for the scheduler thread to reply 2017-12-13 10:41:31 0 [Note] Event Scheduler: Stopped 2017-12-13 10:41:31 0 [Note] Event Scheduler: Purging the queue. 2 events 2017-12-13 10:41:31 0 [Note] unregister_replicator OK 2017-12-13 10:41:31 0 [Note] InnoDB: Starting shutdown... 2017-12-13 10:41:31 0 [Note] InnoDB: Dumping buffer pool(s) to /mysql/xxxxx/data/ib_buffer_pool 2017-12-13 10:41:31 0 [Note] InnoDB: Buffer pool(s) dump completed at 171213 10:41:31 2017-12-13 10:41:32 0 [Note] InnoDB: Shutdown completed; log sequence number 133028285 2017-12-13 10:41:32 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2017-12-13 10:41:32 0 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete However, note the blank line that gets generated when the shutdown begins. it looks like there is an extra "\n" somewhere in the logging which should not be there. Perhaps this can be resolved too?
            sjmudd Simon Mudd added a comment - - edited

            It's not clear to me if or how I can re-open this issue. Perhaps the "blank line on shutdown message bug" needs to go into a separate MDEV? I'm not sure. Clearly that is not a critical or high priority issue but it would be good to clear it up.

            sjmudd Simon Mudd added a comment - - edited It's not clear to me if or how I can re-open this issue. Perhaps the "blank line on shutdown message bug" needs to go into a separate MDEV? I'm not sure. Clearly that is not a critical or high priority issue but it would be good to clear it up.
            serg Sergei Golubchik added a comment -

            I've created MDEV-14639 for the blank line issue.

            serg Sergei Golubchik added a comment - I've created MDEV-14639 for the blank line issue.

            People

              serg Sergei Golubchik
              dthompson David Thompson (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 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.