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.
Log reporting incorrect time
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
-
- Posts: 193
- Joined: Thu May 28, 2015 1:24 am
- Location:
- HTPC Specs:
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
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.
The timestamps in the Event Log are local.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 369
- Joined: Sun Sep 23, 2012 2:54 pm
- Location:
- HTPC Specs:
And who exactly, around the world, is looking at my log ?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.
Revert please. You can always add a Zulu time stamp as a log entry.
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
Not a bad idea, not a bad idea at all ...glorp wrote:You can always add a Zulu time stamp as a log entry.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 1708
- Joined: Fri Aug 24, 2012 7:35 pm
- Location:
- HTPC Specs:
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.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.
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
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
Keeping WMC alive beyond January 2020. https://garyan2.github.io