Reading the log

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
rjj21

Posts: 4
Joined: Wed Feb 08, 2017 2:37 am
Location:

HTPC Specs: Show details

Reading the log

#1

Post by rjj21 » Sun Jun 11, 2017 6:36 pm

Before I post a ticket with Schedules Direct I want to validate I am reading the log entries properly. First question is how do I know how many days were retrieved (I know they should be sending roughly 7 right now). I ask for 30 which probably exceeds their normal capability but I can't seem to find something that says X days were retrieved. Second question is cached descriptions vs. downloaded descriptions. If I am using cached descriptions, does that mean it is using data downloaded before the service disruption? How do I tell if I am receiving what is expected from SD? Third question is if I see "failed to parse", are those specific items I should be reporting to SD? Here is a subset of my log (I removed a bunch of TMDB catalog search entries).

[2017-06-11 18:22:06Z] ===============================================================================
[2017-06-11 18:22:06Z] Beginning epg123 update execution.
[2017-06-11 18:22:06Z] ===============================================================================
[2017-06-11 18:22:06Z] [ INFO] Beginning EPG123 update execution.
[2017-06-11 18:22:06Z] [ INFO] epg123 version 1.1.6 , DaysToDownload: 30 , PrefixEpisodeTitle: False , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: False , AutoAddNew: True
[2017-06-11 18:22:06Z] [ INFO] Successfully retrieved TMDb configurations.
[2017-06-11 18:22:07Z] [ INFO] Token request successful. serverID: 20141201.web.1
[2017-06-11 18:22:07Z] [ INFO] epg123 is up to date. version: 1.1.6
[2017-06-11 18:22:08Z] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[2017-06-11 18:22:08Z] Entering buildLineupServices() for 1 lineups.
[2017-06-11 18:22:08Z] [ INFO] Successfully retrieved the station mapping for lineup USA-CA04507-X.
[2017-06-11 18:22:08Z] Exiting buildLineupServices(). SUCCESS.
[2017-06-11 18:22:08Z] Entering getAllScheduleEntryMd5s() for 30 days on 367 stations.
[2017-06-11 18:22:14Z] [ INFO] Successfully retrieved Md5s for 367 station's daily schedules.
[2017-06-11 18:22:14Z] [WARNG] Failed to parse the schedule Md5 return for stationId 77375 (SPECTSN) on 2017-06-11 and after.
[2017-06-11 18:22:14Z] [WARNG] Failed to parse the schedule Md5 return for stationId 71595 (NGCP) on 2017-06-11 and after.
[2017-06-11 18:22:14Z] [WARNG] Failed to parse the schedule Md5 return for stationId 59054 (MTVCLAP) on 2017-06-11 and after.
[2017-06-11 18:22:14Z] [WARNG] Failed to parse the schedule Md5 return for stationId 70130 (F24EN) on 2017-06-11 and after.

[2017-06-11 18:22:15Z] [ INFO] Found 1888 cached daily schedules.
[2017-06-11 18:22:19Z] [ INFO] Successfully retrieved 363 station's daily schedules.
[2017-06-11 18:22:24Z] [ INFO] Downloaded 2878 daily schedules.
[2017-06-11 18:22:28Z] [ INFO] Processed 4766 daily schedules for 367 stations.
[2017-06-11 18:22:28Z] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[2017-06-11 18:22:28Z] Entering buildAllProgramEntries() for 35948 programs.
[2017-06-11 18:22:36Z] [ INFO] Found 19996 cached program descriptions.
[2017-06-11 18:22:39Z] [ INFO] Successfully retrieved 5000 program descriptions.
[2017-06-11 18:22:49Z] [ INFO] Successfully retrieved 5000 program descriptions.
[2017-06-11 18:22:58Z] [ INFO] Successfully retrieved 5000 program descriptions.
[2017-06-11 18:23:04Z] [ INFO] Successfully retrieved 952 program descriptions.
[2017-06-11 18:23:06Z] [ INFO] Processed 35948 program descriptions.
[2017-06-11 18:23:06Z] Exiting buildAllProgramEntries(). SUCCESS.
[2017-06-11 18:23:06Z] Entering buildAllGenericSeriesInfoDescriptions() for 6089 series.
[2017-06-11 18:23:07Z] [ INFO] Found 4854 cached series descriptions.
[2017-06-11 18:23:08Z] [ INFO] Successfully retrieved 500 generic program descriptions.
[2017-06-11 18:23:08Z] [ INFO] Successfully retrieved 500 generic program descriptions.
[2017-06-11 18:23:09Z] [ INFO] Successfully retrieved 235 generic program descriptions.
[2017-06-11 18:23:09Z] [ INFO] Processed 6089 series descriptions.
[2017-06-11 18:23:09Z] Exiting buildAllGenericSeriesInfoDescriptions(). SUCCESS.
[2017-06-11 18:23:09Z] Entering getAllMoviePosters() for 3630 movies.
[2017-06-11 18:23:09Z] [ INFO] Found 2154 cached movie poster links.
[2017-06-11 18:23:10Z] [ INFO] Successfully retrieved artwork info for 500 programs.
[2017-06-11 18:23:46Z] [ INFO] Processed 3630 movie poster links.
[2017-06-11 18:23:46Z] Exiting getAllMoviePosters(). SUCCESS.
[2017-06-11 18:23:46Z] Entering getAllSeriesImages() for 6089 series.
[2017-06-11 18:23:46Z] [ INFO] Found 4599 cached series image links.
[2017-06-11 18:23:47Z] [ INFO] Successfully retrieved artwork info for 500 programs.
[2017-06-11 18:23:48Z] [ INFO] Successfully retrieved artwork info for 500 programs.
[2017-06-11 18:23:51Z] [ INFO] Successfully retrieved artwork info for 493 programs.
[2017-06-11 18:23:52Z] [ INFO] Processed 6092 series image links.
[2017-06-11 18:23:52Z] Exiting getAllSeriesImages(). SUCCESS.
[2017-06-11 18:23:52Z] [ INFO] Completed compiling keywords and keyword groups.
[2017-06-11 18:23:52Z] Entering writeMxf().
[2017-06-11 18:23:53Z] [ INFO] Completed save of mxf file.
[2017-06-11 18:23:53Z] Exiting writeMxf(). SUCCESS.
[2017-06-11 18:23:53Z] Entering writeImageArchive().
[2017-06-11 18:23:53Z] [ INFO] Completed save of image archive file.
[2017-06-11 18:23:53Z] Exiting writeImageArchive(). SUCCESS.
[2017-06-11 18:23:56Z] [ INFO] 1249 files deleted from the cache directory during cleanup.
[2017-06-11 18:23:56Z] [ INFO] Generated .mxf file contains 367 services, 6089 series, 35948 programs, and 53270 people with 9530 image links.
[2017-06-11 18:23:56Z] [ INFO] Completed EPG123 update execution. SUCCESS.
[2017-06-11 18:23:56Z] [ INFO] epg123 update execution time was 00:01:49.6681927.

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Sun Jun 11, 2017 7:14 pm

rjj21 wrote:Before I post a ticket with Schedules Direct I want to validate I am reading the log entries properly. First question is how do I know how many days were retrieved (I know they should be sending roughly 7 right now). I ask for 30 which probably exceeds their normal capability but I can't seem to find something that says X days were retrieved. Second question is cached descriptions vs. downloaded descriptions. If I am using cached descriptions, does that mean it is using data downloaded before the service disruption? How do I tell if I am receiving what is expected from SD? Third question is if I see "failed to parse", are those specific items I should be reporting to SD? Here is a subset of my log (I removed a bunch of TMDB catalog search entries).

Code: Select all

[2017-06-11 18:22:08Z] Entering getAllScheduleEntryMd5s() for 30 days on 367 stations.
[2017-06-11 18:22:14Z] [ INFO] Successfully retrieved Md5s for 367 station's daily schedules.
[2017-06-11 18:22:14Z] [WARNG] Failed to parse the schedule Md5 return for stationId 77375 (SPECTSN) on 2017-06-11 and after.
[2017-06-11 18:22:14Z] [WARNG] Failed to parse the schedule Md5 return for stationId 71595 (NGCP) on 2017-06-11 and after.
[2017-06-11 18:22:14Z] [WARNG] Failed to parse the schedule Md5 return for stationId 59054 (MTVCLAP) on 2017-06-11 and after.
[2017-06-11 18:22:14Z] [WARNG] Failed to parse the schedule Md5 return for stationId 70130 (F24EN) on 2017-06-11 and after.
[2017-06-11 18:22:15Z] [ INFO] Found 1888 cached daily schedules.
[2017-06-11 18:22:19Z] [ INFO] Successfully retrieved 363 station's daily schedules.
[2017-06-11 18:22:24Z] [ INFO] Downloaded 2878 daily schedules.
[2017-06-11 18:22:28Z] [ INFO] Processed 4766 daily schedules for 367 stations.
[2017-06-11 18:22:28Z] Exiting getAllScheduleEntryMd5s(). SUCCESS.
I'll work on this one since the basic rules apply to all others.

Explanation by line:
1. We entered this part of the code requesting 30 days on 367 stations which would be 11,010 daily schedules
2. We got the response for the above request BUT
3.-6. these stations contained no schedule information <= this should be reported to SD in a trouble ticket (just copy these lines into the ticket to help them out)
7. with the information from the response, we found that we already have 1,888 of the daily schedule information in the cache folder (don't need to download again)
8. states we got schedule information for 363 stations (367 requested minus 4 empty)
9. with the information from the response, we requested and downloaded 2,878 daily schedules that were available from SD and not cached locally
10. We processed all 4,766 daily schedules (1,888 cached plus 2,878 downloaded)
11. done with this part

Because the number of days downloaded of each station can be different, especially if you are requesting 30 days, it is not obvious how many days are downloaded. Doing some math you can figure you are getting 13-14 days worth right now (4,766 daily schedules / 363 stations).

I think that answers most of your questions.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Post Reply