[MDEV-14639] blank line in the error log on shutdown Created: 2017-12-13  Updated: 2017-12-19  Resolved: 2017-12-19

Status: Closed
Project: MariaDB Server
Component/s: Scripts & Clients
Affects Version/s: None
Fix Version/s: 5.5.59, 10.0.34, 10.1.30, 10.2.12, 10.3.3

Type: Bug Priority: Major
Reporter: Sergei Golubchik Assignee: Sergey Vojtovich
Resolution: Fixed Votes: 1
Labels: contribution, foundation


 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.

 Comments   
Comment by Elena Stepanova [ 2017-12-13 ]

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

Comment by Simon Mudd [ 2017-12-13 ]

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

Comment by Simon Mudd [ 2017-12-15 ]

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

Generated at Thu Feb 08 08:15:08 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.