Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

Timestamp issues

by Tanktalus (Canon)
on Jul 10, 2012 at 14:40 UTC ( #980881=monkdiscuss: print w/replies, xml ) Need Help??

jdporter helpfully sent me a note that last hour of cb was out of whack. I don't really know what the problem was (other than a lack of logging! I'll have to add that in as I find time), though the Windows-standard solution worked (restart the daemon, not the whole machine). Then I found this interesting tidbit. The time stamp associated with CB messages is in the future of what my clock says the current time is, by over 2 minutes. Corion pointed out the Tick Tock nodelet, and I noticed that the CB message time stamp is in the future of what PM says the current time is as well.

Maybe there's a server involved somewhere here where the ntp daemon isn't running/working, keeping the timestamps in sync?

Corion also seemed to suggest that the Tick Tock nodelet maybe should use select NOW() from dual instead of the localtime, but I'm not sure what type of extra hit the db would take on something like that. A working ntp daemon seems more prudent to me :-)

Note that the only effect this has on last hour of cb that I can be sure of is that anything from the future gets excluded in my SQL: "STAMP > ? AND STAMP <= ?" (so that messages that come in while I'm processing all this don't get included later).

While writing this, Athanasius also suggested in the CB that "Someone just posted a node “-3 seconds ago” !" - so the aesthetic effect is a bit bigger than just what I noticed. :-)

Replies are listed 'Best First'.
Re: Timestamp issues
by zentara (Archbishop) on Jul 10, 2012 at 16:03 UTC
    It just may be coincidence, but now that I read your post, I tried to login today around 10:30 and got Server Error messages. It lasted about 5 minutes.

    I'm not really a human, but I play one on earth.
    Old Perl Programmer Haiku ................... flash japh
Re: Timestamp issues (filed)
by tye (Sage) on Jul 10, 2012 at 17:06 UTC

    DB server's clock is running about 2 minutes fast right now. Support ticket filed.

    - tye        

      Ticket has progressed to a replacement of the motherboard to get a less over-speed hardware clock. This will likely mean a site outage. I'll update when I have more details on schedule and expected duration.

      - tye        

Re: Timestamp issues
by Old_Gray_Bear (Bishop) on Jul 10, 2012 at 18:10 UTC
    According to Saints in Our Book, I was last here "-88 seconds ago" ....

    I Go Back to Sleep, Now.


      Perhaps that was because you were having "40 winks"!

Re: Timestamp issues
by Argel (Prior) on Jul 11, 2012 at 20:43 UTC

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: monkdiscuss [id://980881]
Approved by marto
[haukex]: Morning!

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (6)
As of 2017-12-15 07:43 GMT
Find Nodes?
    Voting Booth?
    What programming language do you hate the most?

    Results (421 votes). Check out past polls.