You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The timestamps in the server logs are not correct.
Example for ARM: -748823 Jan 1970 -19:-36:00.145
Example for x86: 28 Jul 2015 07:49:05.074
On ARM, the timestamps are wrong because the gettimeofday call does not function properly.
On x86, I tracked it down to this call to the redis version of localtime with the server.timezone parameter, which is subtracted from the timestamp. The server.timezone variable has the value 263675520, which corresponds to a shift of about 8 years, consistent with the change from 2023 to 2015.
The text was updated successfully, but these errors were encountered:
The timestamps in the server logs are not correct.
Example for ARM:
-748823 Jan 1970 -19:-36:00.145
Example for x86:
28 Jul 2015 07:49:05.074
On ARM, the timestamps are wrong because the gettimeofday call does not function properly.
On x86, I tracked it down to this call to the
redis
version oflocaltime
with theserver.timezone
parameter, which is subtracted from the timestamp. Theserver.timezone
variable has the value 263675520, which corresponds to a shift of about 8 years, consistent with the change from 2023 to 2015.The text was updated successfully, but these errors were encountered: