Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #11431

Closed (moved)
(moved)
Open
Created Apr 07, 2014 by Karsten Loesing@karsten

Possible time-zone problem with computing uptimes and downtimes

Could it be that Globe interprets last_seen and last_restarted as datetimes in the user's local timezone?

I looked up a random non-running relay and found the following line in its Onionoo details file:

"last_seen":"2014-04-07 08:00:00",

It was 18:26:00 CEST when I looked up the relay in Globe, so 16:26:00 UTC. Globe told me the downtime was 10 hours 26 minutes. But it should have said 8 hours 26 minutes.

Similarly, I looked up another random relay, but this time one that was running. It's Onionoo details file contained this line:

"last_restarted":"2014-04-07 09:18:05"

I looked it up in Globe at 18:31:00 CEST, so 16:31:00 UTC, and Globe told me the uptime is 9 hours 13 minutes. It should have said 7 hours 13 minutes.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking