Bug #78475 mysqld_safe error log timestamp differs with mysqld error log
Submitted: 18 Sep 2015 5:28 Modified: 8 Dec 2015 18:31
Reporter: Ramana Yeruva Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:5.6.27 OS:Any
Assigned to: CPU Architecture:Any

[18 Sep 2015 5:28] Ramana Yeruva 
Description:
start/stop mysqld service on EL7,Debian/ubuntu platforms with repo packages and observe error.log or mysqld.log and see time stamp of mysqld_safe shows

How to repeat:
2015-09-18 06:44:11 8503 [Note] Shutting down plugin 'mysql_old_password'
2015-09-18 06:44:11 8503 [Note] Shutting down plugin 'mysql_native_password'
2015-09-18 06:44:11 8503 [Note] Shutting down plugin 'binlog'
2015-09-18 06:44:11 8503 [Note] /usr/sbin/mysqld: Shutdown complete

150918 06:44:11 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended<--can this be correctly formatted with right format..?
150918 06:47:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2015-09-18 06:47:49 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please us
[8 Dec 2015 18:31] Paul DuBois 
Noted in 5.7.11, 5.8.0 changelogs.

The format of log output produced by mysqld_safe now is configurable
using the --mysqld-safe-log-timestamps option. This option can be
used to produce log timestamps in formats compatible with the server
or in formats used by mysqld_safe in older versions of MySQL.