Ticket #4282 (closed defect: fixed)

Opened 3 years ago

Last modified 3 months ago

Server time wrong

Reported by: opty Owned by:
Priority: major Milestone:
Component: adm Version:
Keywords: Cc:
Blocked By: Blocking:
Branch state: no branch Votes for changeset:

Description

Please, correct the server time. It seems about 3 minutes behind.

Change History

comment:1 Changed 3 years ago by andrew_b

  • Status changed from new to closed
  • Resolution set to fixed

comment:2 Changed 4 months ago by opty

  • Status changed from closed to reopened
  • Resolution fixed deleted

The time seems about half a minute behind again.

comment:3 Changed 3 months ago by zaytsev

  • Status changed from reopened to closed
  • Resolution set to fixed

Done, out of curiosity, how do you notice that?

[root@midnightcommander ~]# date && ntpdate 0.us.pool.ntp.org && date
Thu Jun 27 10:25:29 UTC 2024
27 Jun 10:26:07 ntpdate[27724]: step time server 198.60.22.240 offset 37.180526 sec
Thu Jun 27 10:26:07 UTC 2024

We run in a VM, so normally clock should be taken care of by the host system. I wonder why the drift o_O

comment:4 Changed 3 months ago by opty

E.g. by comparing the time of submit and the time from link after Changed.

Probably some host system (virtualization technology, configuration...) issue.

comment:5 Changed 3 months ago by zaytsev

Well, posting takes about 30 seconds, which a known issue, but I was not able to pinpoint where exactly and why it hangs so far (unfortunately). It seems to have something to do with sending e-mail notifications, but the MTA is not managed by us, and I think the best solution would be to finally decommission this old and halfway broken machine and move to GitHub, instead of investing disproportional amount of time in cleaning it up and trying to investigate these issues. That was to say, that submission time is not a good indicator of the clock drift.

I was rather wondering which consequences does the drift have for you in practice, but apparently the answer is that you've noticed it and decided to report it even though it doesn't have any immediate ramifications.

comment:6 Changed 3 months ago by opty

Yeah, I noticed some delay (DNS?) but I'd expect the time to go forth instead of back in that case.

Most likely nothing serious unless you start to try to correlate things, rather that I like precise time where easily available.

comment:7 Changed 3 months ago by zaytsev

I don't know what the delay is all about for the life of me. Maybe some spam checking / DNS resolution thing... as I say, better invest time into setting up something new and migrating properly, than patching stuff that is falling apart - unless there is no other choice to get by.

Note: See TracTickets for help on using tickets.