Mysql5.7錯誤日誌時間不對的解決辦法

甲骨文技術支援發表於2017-01-06

 MySQL 5.7的錯誤日誌時間和系統時間不一致,看起來費勁,查閱官方文件得知MySQL 5.7.2 開始,新增了 log_timestamps 引數,它主要是控制 error log、genera log等日誌檔案的顯示時間引數:
官文如下:

This variable controls the timestamp time zone of error log messages, and of general query log and slow query log messages written to files. It does not affect the time zone of general query log and slow query log messages written to tables (mysql.general_log, mysql.slow_log). Rows retrieved from those tables can be converted from the local system time zone to any desired time zone with CONVERT_TZ() or by setting the session time_zone system variable.

Permitted log_timestamps values are UTC (the default) and SYSTEM (local system time zone).

Timestamps are written using ISO 8601 / RFC 3339 format: YYYY-MM-DDThh:mm:ss.uuuuuu plus a tail value of Z signifying Zulu time (UTC) or ±hh:mm (an offset from UTC).

This variable was added in MySQL 5.7.2. Before 5.7.2, timestamps in log messages were written using the local system time zone by default, not UTC. If you want the previous log message time zone default, set log_timestamps=SYSTEM.

做了如下修改後,顯示正常了:

點選(此處)摺疊或開啟

  1. (root@localhost) [(none)]> show global variables like 'log_timestamps';
  2. +----------------+-------+
  3. | Variable_name | Value |
  4. +----------------+-------+
  5. | log_timestamps | UTC |
  6. +----------------+-------+
  7. 1 row in set (0.01 sec)

  8. (root@localhost) [(none)]> set global log_timestamps=SYSTEM;
  9. Query OK, 0 rows affected (0.00 sec)

  10. (root@localhost) [(none)]> SHOW global variables like 'log_timestamps';
  11. +----------------+--------+
  12. | Variable_name | Value |
  13. +----------------+--------+
  14. | log_timestamps | SYSTEM |
  15. +----------------+--------+
  16. 1 row in set (0.01 sec)





來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/20893244/viewspace-2132032/,如需轉載,請註明出處,否則將追究法律責任。

相關文章