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

blank line in the error log on shutdown

Details

    Description

      After MDEV-14337 error log looks like

      ....
      		 
      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

      The blank line should not be there.

      See also comments in MDEV-14488.

      Attachments

        Activity

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

          For a note, it's not new, it has been there for a long, long time. E.g. 10.0.13:

          170916  0:35:15 [Note] /data/releases/10.0.13/bin/mysqld: ready for connections.
          		 
          Version: '10.0.13-MariaDB'  socket: '/tmp/mysql.sock'  port: 3306  MariaDB Server
          		 
          170916  0:35:24 [Note] /data/releases/10.0.13/bin/mysqld: Normal shutdown
          		 
           
          		 
          170916  0:35:24 [Note] Event Scheduler: Purging the queue. 0 events

          Or even on MySQL 5.0.96:

          Version: '5.0.96'  socket: '/tmp/mysql.sock'  port: 3309  MySQL Community Server (GPL)
          		 
          170825 18:06:53 [Warning] option 'max_tmp_tables': unsigned value 0 adjusted to 1
          		 
          170825 23:07:47 [Note] /data/releases/mysql-5.0.96/bin/mysqld: Normal shutdown
          		 
           
          		 
          170825 23:07:47  InnoDB: Starting shutdown...
          		 
          170825 23:07:48  InnoDB: Shutdown completed; log sequence number 0 43655
          		 
          170825 23:07:48 [Note] /data/releases/mysql-5.0.96/bin/mysqld: Shutdown complete

          elenst Elena Stepanova added a comment - For a note, it's not new, it has been there for a long, long time. E.g. 10.0.13: 170916 0:35:15 [Note] /data/releases/10.0.13/bin/mysqld: ready for connections. Version: '10.0.13-MariaDB' socket: '/tmp/mysql.sock' port: 3306 MariaDB Server 170916 0:35:24 [Note] /data/releases/10.0.13/bin/mysqld: Normal shutdown   170916 0:35:24 [Note] Event Scheduler: Purging the queue. 0 events Or even on MySQL 5.0.96: Version: '5.0.96' socket: '/tmp/mysql.sock' port: 3309 MySQL Community Server (GPL) 170825 18:06:53 [Warning] option 'max_tmp_tables': unsigned value 0 adjusted to 1 170825 23:07:47 [Note] /data/releases/mysql-5.0.96/bin/mysqld: Normal shutdown   170825 23:07:47 InnoDB: Starting shutdown... 170825 23:07:48 InnoDB: Shutdown completed; log sequence number 0 43655 170825 23:07:48 [Note] /data/releases/mysql-5.0.96/bin/mysqld: Shutdown complete
          sjmudd Simon Mudd added a comment -

          Yep it's been there for a long time. Doesn't mean it is not a bug.... (also an issue upstream iirc).

          sjmudd Simon Mudd added a comment - Yep it's been there for a long time. Doesn't mean it is not a bug.... (also an issue upstream iirc).
          sjmudd Simon Mudd added a comment -

          See: https://github.com/MariaDB/server/pull/515

          sjmudd Simon Mudd added a comment - See: https://github.com/MariaDB/server/pull/515

          People

            svoj Sergey Vojtovich
            serg Sergei Golubchik
            Votes:
            1 Vote for this issue
            Watchers:
            3 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.