Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: 32bit Systems - Year 2038 (Y2K38) |
|
| Author |
|
TheFutureIsNow
Joined: 07 Oct 2025
Posts: 1
|
 Posted: Tue 07 Oct '25 11:48 Post subject: 32bit Systems - Year 2038 (Y2K38) |
 |
|
During testing I saw some weird behavior with the Apache Webserver when setting the system time on my 32bit Debian system above the 19 January 2038. The system is set up to support 64bit time. Used Version of Apache2 were 2.4.56 and after updating 2.4.65.
Main weird behavior:
The timestamps of log entries in apache.log/error.log are
wrong and inconsistent (Years displayed are 1901, 1969, 1970, 2037,...) between different modules.
The server time returned in http requests is constant, false and doesnt change.
The module mod_reqtimeout doesnt work and almost always generates timeouts, blocking connection altogether (when it is disabled connections seem to work normal).
The only mention of Y2K38 in https://www.apachelounge.com/changelog-2.4.html I could find is:
rotatelogs: Fix expansion of %Z in localtime (-l) mode, and fix Y2K38 bug.
So my question is two-fold:
Does 32 Bit Apache currently fully support time settings above the 19 January 2038, if yes how can I make use of that?
If no, is it planned to include the necessary changes to fix Y2K38 problems in the future? |
|
| Back to top |
|
|
|
|
|
|
