Bug #94139 The first few lines of the error log with wrong timezone when start mysqld
Submitted: 30 Jan 2019 12:39 Modified: 31 Jan 2019 7:46
Reporter: ashe sun (OCA) Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Logging Severity:S3 (Non-critical)
Version:5.7.18, 5.7.25 OS:Any
Assigned to: CPU Architecture:Any
Tags: Contribution

[30 Jan 2019 12:39] ashe sun
The relevant variables
#err log timestamps
# values of table_open_cache_instances is not appropriate
table_open_cache_instances = 128

My OS  timezone:
ashe@ubuntu:~$ date -R
Wed, 30 Jan 2019 20:32:24 +0800 

And start mysqld with these variables,the output of error log:

2019-01-30T12:35:10.373167Z 0 [Warning] option 'table_open_cache_instances': unsigned value 128 adjusted to 64
2019-01-30T20:35:10.544561+08:00 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-01-30T20:35:10.544629+08:00 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.

The first line of the error log with wrong timezone. The second line is correct.

How to repeat:
As Description.

Suggested fix:
I will upload my patch file.
[30 Jan 2019 12:41] ashe sun

Attachment: errlog_timezone.patch (application/octet-stream, text), 3.11 KiB.

[30 Jan 2019 13:03] MySQL Verification Team
Hello ashe,

Thank you for the report and contribution.
Please ensure to re-send the patch via that tab. Otherwise we would not be able to accept it.

[30 Jan 2019 13:43] ashe sun
The first few lines of the error log with wrong timezone patch file.

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: errlog_timezone.patch (application/octet-stream, text), 3.11 KiB.

[31 Jan 2019 1:29] seung ho Jung
How to apply the patch!!
I installed mysql-5.7.25-linux-glibc2.12-x86_64.tar.gz

No find sys_vars.cc file
[31 Jan 2019 7:46] ashe sun
Hello seung
Use source code Package