Spider-VP Spiral Patches (MDEV-14509)

[MDEV-14488] logging not happening on spider branch builds Created: 2017-11-23  Updated: 2020-08-25  Resolved: 2017-12-13

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

Type: Technical task Priority: Major
Reporter: David Thompson (Inactive) Assignee: Sergei Golubchik
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Duplicate
duplicates MDEV-14889 Server fails to start because of aria... Closed
is duplicated by MDEV-14337 mysqld_safe may suppress error messag... Closed
Relates
relates to MDEV-14714 mysqld writes status information on H... Closed

 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.

 Comments   
Comment by Simon Mudd [ 2017-11-24 ]

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.

Comment by Sergei Golubchik [ 2017-11-27 ]

Fixed in MDEV-14337

Comment by Simon Mudd [ 2017-12-13 ]

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?

Comment by Simon Mudd [ 2017-12-13 ]

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.

Comment by Sergei Golubchik [ 2017-12-13 ]

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

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