Bug #83374 MySQL Year 2038

• Submitted: 13 Oct 2016 15:58
• Modified: 13 Oct 2016 22:00
• Reporter: Jitesh Yadav
• Status: Unsupported
• Category: MySQL Server: DML
• Severity: S2 (Serious)
• Version: 5.7.14
• OS: Red Hat (64 Bit)
• CPU Architecture: Any

[13 Oct 2016 15:58] Jitesh Yadav

Description:
I am using MySQL 5.5. For some reason, I need to change the date of my system to after 2038. Unfortunately, the MySQL service won't start after the year 2038:

If i change the system date to any of the dates after year 2038. I get the following  error message.

610924 18:59:16[ERROR] This MySQL server doesn't support dates later then 2038
610924 18:59:16 [ERROR] Aborting

I am using 64 bit MySQL. 

Please help.

How to repeat:
To repeat please do the following restart method.

root@sd-84962:~# date
Sat Sep 24 18:41:32 CEST 2039
root@sd-84962:~# service mysql restart
stop: Unknown instance:
start: Job failed to start
root@sd-84962:~# date -s "Tue Sep 24 18:37:56 CEST 2015"
Thu Sep 24 18:37:56 CEST 2015
root@sd-84962:~# service mysql restart
stop: Unknown instance:
mysql start/running, process 22123

returns following error message 
610924 18:59:16[ERROR] This MySQL server doesn't support dates later then 2038
610924 18:59:16 [ERROR] Aborting

[13 Oct 2016 17:49] MySQL Verification Team

https://dev.mysql.com/worklog/task/?id=1872

[13 Oct 2016 22:00] MySQL Verification Team

Thank you for the bug report. Currently that kind of date aren't supported.