|
|
#1
August 11, 2014, 05:42:29 PM
|
||||
|
||||
Site going down for a few minutes tonight to resynchronize the clock
As some of you might have noticed, the clock is gradually drifting forward. In fact, it's approximately four minutes ahead of the actual time. I cannot simply resynchronize it now because it would cause posts to appear out of order if any are made close to the synchronization point, as the clock will move back four minutes to its proper place. For that reason, at 11 PM PST tonight (that's in roughly 5˝ hours), I will be shutting down the site for about five minutes to fix the clock.
This applies to all of the Victory Road Network. Last edited by Cat333Pokémon; August 11, 2014 at 05:43:40 PM. |
|
#2
August 11, 2014, 05:57:09 PM
|
||||
|
||||
|
Out of curiosity, how did this end up happening?
|
|
#3
August 11, 2014, 06:16:55 PM
|
||||
|
||||
|
On Debian/Ubuntu servers, by default there is no automatic clock synchronization, because if the clock syncs during an active transaction, particularly if during multiple transactions (in this case, a transaction is writing something to the database), it could cause a problem if the entries are out of order. It means very little on, say, a forum, but someone running a business could be liable for having database entries out of order.
Quartz clocks, like the ones in computers, are rather accurate, but they do lose or gain small amounts of time over long periods, so they need to be re-set every now and then. Windows, for instance, attempts to synchronize every week or two. |
|
#4
August 12, 2014, 12:32:05 AM
|
||||
|
||||
|
I had to do it a little later than desired, but it's so weird seeing the time go backward:
Code:
$ date Tue Aug 12 00:29:52 PDT 2014 $ sudo ntpdate pool.ntp.org 12 Aug 00:25:47 ntpdate[15731]: step time server 204.2.134.164 offset -249.769222 sec Code:
$ sudo ntpdate pool.ntp.org 12 Aug 00:31:12 ntpdate[16484]: adjust time server 204.2.134.164 offset 007809 sec 
Last edited by Cat333Pokémon; August 12, 2014 at 12:32:43 AM. |
