-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.0.beta
-
None
-
No
-
Important
-
rhel-sst-cs-databases
-
None
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
None
-
None
-
None
What were you trying to do that didn't work?
A customer tried starting mariadb after changing the date to year 2038. It appears that the service won't start, complaining with:
2038-01-31 13:00:03 0 [ERROR] This server doesn't support dates later than 2038
This is problematic, because, even through RHEL10 won't be supported anymore, it's very possible that embedded devices still execute it.
Please hence try fixing this ASAP.
Please provide the package NVR for which bug is seen:
mariadb-server-10.11.9-3.el10.x86_64
How reproducible:
Always
Steps to reproduce
- Change the date to Jan 31, 2038
# date 013113002038
- Start the service
Expected results
Starts properly
Actual results
Fails
- clones
-
RHEL-57666 mariadb won't start after Jan, 2038
- New