Bug #69254 different datetime-format between mysqld and mysqld_safe
Submitted: 16 May 2013 7:37 Modified: 8 Nov 2016 3:23
Reporter: Tsubasa Tanaka (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Logging Severity:S3 (Non-critical)
Version:5.6.11 OS:Linux
Assigned to: CPU Architecture:Any

[16 May 2013 7:37] Tsubasa Tanaka
Description:
mysqld changes datetime-format in its error log, new datetime-format has 4 disits year and "-" separators.
But mysqld_safe still keeps old datetime-format, which has 2 disits year and no separators.

MySQL 5.5.31

130516 15:58:39 mysqld_safe Starting mysqld daemon with databases from /usr/mysql/5.5.31/data
130516 15:58:39 [Note] Plugin 'FEDERATED' is disabled.
130516 15:58:39 [Warning] option 'innodb-buffer-pool-size': signed value 3145728 adjusted to 5242880
..

MySQL 5.6.11

130516 15:53:27 mysqld_safe Starting mysqld daemon with databases from /usr/mysql/5.6.11/data
2013-05-16 15:53:27 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timest
amp server option (see documentation for more details).
2013-05-16 15:53:27 1552 [Note] Plugin 'FEDERATED' is disabled.
2013-05-16 15:53:27 1552 [Warning] option 'innodb-buffer-pool-size': signed value 3145728 adjusted to 5242880
..

How to repeat:
run mysqld_safe and see your error log.

Suggested fix:
*** scripts/mysqld_safe.sh.org  2013-04-05 21:27:18.000000000 +0900
--- scripts/mysqld_safe.sh      2013-05-16 16:01:26.447776836 +0900
***************
*** 122,128 ****
    priority="$1"
    shift

!   msg="`date +'%y%m%d %H:%M:%S'` mysqld_safe $*"
    echo "$msg"
    case $logging in
      init) ;;  # Just echo the message, don't save it anywhere
--- 122,128 ----
    priority="$1"
    shift

!   msg="`date +'%Y-%m-%d %H:%M:%S'` $$ mysqld_safe $*"
    echo "$msg"
    case $logging in
      init) ;;  # Just echo the message, don't save it anywhere
[16 May 2013 8:01] MySQL Verification Team
Thank you for the feature request and contribution.
[8 Nov 2016 3:23] Tsubasa Tanaka
This has been fixed by Bug#78475, I close this.