Log reporting incorrect time

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
Post Reply
DOS4EVER

Posts: 193
Joined: Thu May 28, 2015 1:24 am
Location:

HTPC Specs: Show details

Log reporting incorrect time

#1

Post by DOS4EVER » Mon Jun 12, 2017 2:42 pm

My log is reporting the incorrect time; it seems to be five hours ahead. My PC date and time are correct.

It should read 09:36...

[2017-06-12 14:36:41Z] ===============================================================================
[2017-06-12 14:36:41Z] Activating the epg123 configuration GUI.
[2017-06-12 14:36:41Z] ===============================================================================
[2017-06-12 14:36:42Z] [ INFO] epg123 is up to date. version: 1.1.6
[2017-06-12 14:36:43Z] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 6/12/2017 7:59:59 AM; Exit: 0x00000000
[2017-06-12 14:36:43Z] [ INFO] Token request successful. serverID: 20141201.web.1
[2017-06-12 14:36:43Z] [ INFO] Status request successful. account expires: 2018-06-19T00:38:18Z , lineups: 1/4 , lastDataUpdate: 2017-06-12T05:27:14Z
[2017-06-12 14:36:43Z] [ INFO] system status: Online , message: No known issues.
[2017-06-12 14:36:43Z] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[2017-06-12 14:36:43Z] [ INFO] Successfully retrieved the station mapping for lineup USA-TN54558-X.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#2

Post by garyan2 » Mon Jun 12, 2017 2:51 pm

The log is reporting Zulu/GMT/UTC time. This was intentional but will probably change back to local in next release... it just helps out when looking at log files from around the world to see when events actually occurred.

The timestamps in the Event Log are local.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

glorp

Posts: 369
Joined: Sun Sep 23, 2012 2:54 pm
Location:

HTPC Specs: Show details

#3

Post by glorp » Mon Jun 12, 2017 2:56 pm

garyan2 wrote:The log is reporting Zulu/GMT/UTC time. it just helps out when looking at log files from around the world to see when events actually occurred.
And who exactly, around the world, is looking at my log ?
:D

Revert please. You can always add a Zulu time stamp as a log entry.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#4

Post by garyan2 » Mon Jun 12, 2017 5:43 pm

glorp wrote:You can always add a Zulu time stamp as a log entry.
Not a bad idea, not a bad idea at all ... :thumbup:
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Sammy2

Posts: 1708
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

#5

Post by Sammy2 » Tue Jun 13, 2017 2:30 pm

garyan2 wrote:The log is reporting Zulu/GMT/UTC time. This was intentional but will probably change back to local in next release... it just helps out when looking at log files from around the world to see when events actually occurred.

The timestamps in the Event Log are local.
I see. SiliconDust does the same thing in their tuner logs. Bugs the hell out of me but I never report logs back to them because I just don't have to. I can see where you'd like consistent times when you're looking at people reporting logs here I think. Maybe not. I'm not sure why that would make a difference? Thanks.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#6

Post by garyan2 » Tue Jun 13, 2017 5:06 pm

Next rev will be back to local time ... just added an entry in the log with to record GMT as suggested.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Post Reply