Temporary Clock Problem

[Mod 7]

There seems to be a problem with the clock. Instead of advancing the system's clock by 1 hour, someone made a mistake and set it back by 11 hours. The system now thinks it's 2:21 AM as opposed to 2:21 PM.

I have contacted Fred Zed to have this fixed ASAP. No need to PM the Mods.

Some of you might experience problems with the search function if you happen to have had a search in progress when the clock was updated. You would get a message saying you have to wait 42,000 seconds for your next search (or something similar). This is a result of internal vBulletin counters mixed up by backtracking the clock. I unfortunately can't do anything for you. As far as I know, you will have to wait the specified number of seconds, or Fred to fix the clock, whichever comes first.

Sorry for the inconvenience.

M7

 

[EagerBeaver]

Tell Fred he needs to fix this ASAP because if people can't click on "new posts" due to this clock problem and are getting the whacked out message I am getting, posting is going to drop precipitously because you cannot post on that which you cannot see.

 

[Mod 7]

I already did. Thanks.

M7

 

[Fred Zed]

There is a server problem right now and it should be corrected soon. It's affecting TERB and PERB as well.

Scroll back 12 hours in the posting times and you will see current posts.

I reported the problem already, it should be fixed any time now

 

[z/m(Ret)]

With my most reent posts being shifted around the timeline, I felt like Marcel of Proust's A la recherche du temps perdu.

 

[EagerBeaver]

It has been fixed.

 

[Mod 7]

With my most reent posts being shifted around the timeline, I felt like Marcel of Proust's A la recherche du temps perdu.

Because the clock was wrong. Imagine what you could have done with those 12 hours in twilight zone, had you known in advance.

Thread closed. Thanks for your patience.

M7