EPG123 v1.1.3 - first night's update failed?

[DSperber]

Well, this was unexpected.

I upgraded from v1.1.1 to v1.1.3 yesterday afternoon. Simply ran the updater/installer within C:\EPG123 so that the replaced files went right there. No problems.

Today, looking at this forum, I saw a new thread that said WMC crashes looking at the Guide after upgrading to v1.1.3, which didn't happen to me yesterday. But I checked again, just to be sure. Still no crash for me. Guide and WMC overall works perfectly.

Then I decided to check the log from last night, just to be sure that my regular 2AM update went without a hitch. Well, there was a hitch! It started, but never seemingly finished.

I just a few minutes ago manually ran SAVE + EXECUTE just to see if it would also fail again, but it didn't. It seemed to work perfectly.

So I don't know what happened last night, but I will definitely check again tomorrow to see if tonight's update again hangs like it did last night, or if it works perfectly and last night's experience was just a fluke.

Just for reference, here is the log from two nights ago, when I was still running v1.1.1.

Code: Select all

[3/6/2017 2:00:00 AM] ===============================================================================
[3/6/2017 2:00:00 AM]  Beginning epg123 update execution.
[3/6/2017 2:00:00 AM] ===============================================================================
[3/6/2017 2:00:02 AM] [ INFO] Successfully retrieved TMDb configurations.
[3/6/2017 2:00:02 AM] [ INFO] epg123 version 1.1.1 , DaysToDownload: 28 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: True , AutoAddNew: True
[3/6/2017 2:00:02 AM] [ INFO] Token request successful. serverID: 20141201.web.3
[3/6/2017 2:00:03 AM] [ INFO] epg123 is not up to date. Latest version is 1.1.3 and can be downloaded from http://epg123.garyan2.net.
[3/6/2017 2:00:03 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[3/6/2017 2:00:03 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[3/6/2017 2:00:04 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[3/6/2017 2:00:04 AM] Entering getAllScheduleEntryMd5s() for 28 days on 83 stations.
[3/6/2017 2:00:17 AM] [ INFO] Successfully retrieved Md5s for 83 station's daily schedules.
[3/6/2017 2:00:24 AM] [ INFO] Successfully retrieved 83 station's daily schedules.
[3/6/2017 2:00:30 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[3/6/2017 2:00:30 AM] Entering buildAllProgramEntries() for 16312 programs.
[3/6/2017 2:01:10 AM] [ INFO] Successfully retrieved 972 programs metadata.
[3/6/2017 2:01:13 AM] Exiting buildAllProgramEntries(). SUCCESS.
[3/6/2017 2:01:13 AM] Entering buildAllGenericSeriesInfoDescriptions() for 2208 series.
[3/6/2017 2:01:18 AM] [ INFO] Successfully retrieved 62 programs generic description metadata.
[3/6/2017 2:01:18 AM] Exiting buildAllGenericSeriesInfoDescriptions(). SUCCESS.
[3/6/2017 2:01:18 AM] Entering getAllMoviePosters() for 1744 movies.
[3/6/2017 2:01:19 AM] [ INFO] Successfully retrieved artwork info for 142 programs.
[3/6/2017 2:01:20 AM] [ INFO] TMDb catalog search for "Stalker's Prey" from 2017 found 0 results.
[3/6/2017 2:01:20 AM] [ INFO] TMDb catalog search for "Stalker's Prey" from 2018 found 0 results.
[3/6/2017 2:01:21 AM] [ INFO] TMDb catalog search for "Stalker's Prey" from 2016 found 0 results.
[3/6/2017 2:01:21 AM] [ INFO] TMDb catalog search for "American Jihad" from 2017 found 1 results.
[3/6/2017 2:01:21 AM] [ INFO] TMDb catalog search for "My Sweet Audrina" from 2016 found 1 results.
[3/6/2017 2:01:21 AM] [ INFO] TMDb catalog search for "A Story From Chikamatsu" from 1954 found 0 results.
[3/6/2017 2:01:21 AM] [ INFO] TMDb catalog search for "A Story From Chikamatsu" from 1955 found 0 results.
[3/6/2017 2:01:21 AM] [ INFO] TMDb catalog search for "A Story From Chikamatsu" from 1953 found 0 results.
[3/6/2017 2:01:21 AM] Exiting getAllMoviePosters(). SUCCESS.
[3/6/2017 2:01:21 AM] Entering getAllSeriesImages() for 2208 series.
[3/6/2017 2:01:25 AM] [ INFO] Successfully retrieved artwork info for 361 programs.
[3/6/2017 2:01:26 AM] Exiting getAllSeriesImages(). SUCCESS.
[3/6/2017 2:01:26 AM] Entering writeMxf().
[3/6/2017 2:01:26 AM] Exiting writeMxf(). SUCCESS.
[3/6/2017 2:01:26 AM] Entering writeImageArchive().
[3/6/2017 2:01:26 AM] Exiting writeImageArchive(). SUCCESS.
[3/6/2017 2:01:28 AM] [ INFO] 1328 files deleted from the cache directory during cleanup.
[3/6/2017 2:01:28 AM] [STATS] Generated .mxf file contains 83 services, 2208 series, 16312 programs, and 32326 people with 3886 image links.
[3/6/2017 2:01:28 AM] [STATS] epg123 update execution time was 00:01:27.2500000.
[3/6/2017 2:01:28 AM] ====================== Beginning epg123 client execution. =====================
[3/6/2017 2:01:28 AM] [ INFO] Import=True , Match=True , NoLogo=False
[3/6/2017 2:01:28 AM] [ INFO] import filename = epg123.mxf
[3/6/2017 2:01:54 AM] [ INFO] Successfully imported .mxf file into Media Center. Exit code: 0
[3/6/2017 2:01:56 AM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[3/6/2017 2:01:56 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[3/6/2017 2:01:56 AM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[3/6/2017 2:01:56 AM] [STATS] epg123Client mxf load and database reindex execution time was 00:00:27.8800000.
[3/6/2017 2:01:56 AM] ====================== Completed epg123 client execution. =====================
[3/7/2017 2:00:00 AM] ===============================================================================
[3/7/2017 2:00:00 AM]  Beginning epg123 update execution.
[3/7/2017 2:00:00 AM] ===============================================================================
[3/7/2017 2:15:07 AM] ===============================================================================
[3/7/2017 2:15:08 AM]  Beginning epg123 update execution.
[3/7/2017 2:15:08 AM] ===============================================================================
[3/7/2017 2:15:08 AM] [ INFO] Successfully retrieved TMDb configurations.
[3/7/2017 2:15:08 AM] [ INFO] epg123 version 1.1.3 , DaysToDownload: 28 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: True , AutoAddNew: True
[3/7/2017 2:15:09 AM] [ INFO] Token request successful. serverID: 20141201.web.3
[3/7/2017 2:15:09 AM] [ INFO] epg123 is up to date. version: 1.1.3
[3/7/2017 2:15:09 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[3/7/2017 2:15:10 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[3/7/2017 2:15:11 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[3/7/2017 2:15:11 AM] Entering getAllScheduleEntryMd5s() for 28 days on 83 stations.
[3/7/2017 2:15:28 AM] [ INFO] Successfully retrieved Md5s for 83 station's daily schedules.
[3/7/2017 2:15:42 AM] [ INFO] Successfully retrieved 83 station's daily schedules.
[3/7/2017 2:15:50 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[3/7/2017 2:15:50 AM] Entering buildAllProgramEntries() for 16001 programs.

And here is the log from last night's 2AM update. Note that there seems to have been a hiccup at 2AM, and it seems to have self-rescheduled itself to run 15 minutes later at 2:15AM, when it appears to have started again. And it was that 2:15AM update that never finished.

Code: Select all

[3/7/2017 2:00:00 AM] ===============================================================================
[3/7/2017 2:00:00 AM]  Beginning epg123 update execution.
[3/7/2017 2:00:00 AM] ===============================================================================
[3/7/2017 2:15:07 AM] ===============================================================================
[3/7/2017 2:15:08 AM]  Beginning epg123 update execution.
[3/7/2017 2:15:08 AM] ===============================================================================
[3/7/2017 2:15:08 AM] [ INFO] Successfully retrieved TMDb configurations.
[3/7/2017 2:15:08 AM] [ INFO] epg123 version 1.1.3 , DaysToDownload: 28 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: True , AutoAddNew: True
[3/7/2017 2:15:09 AM] [ INFO] Token request successful. serverID: 20141201.web.3
[3/7/2017 2:15:09 AM] [ INFO] epg123 is up to date. version: 1.1.3
[3/7/2017 2:15:09 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[3/7/2017 2:15:10 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[3/7/2017 2:15:11 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[3/7/2017 2:15:11 AM] Entering getAllScheduleEntryMd5s() for 28 days on 83 stations.
[3/7/2017 2:15:28 AM] [ INFO] Successfully retrieved Md5s for 83 station's daily schedules.
[3/7/2017 2:15:42 AM] [ INFO] Successfully retrieved 83 station's daily schedules.
[3/7/2017 2:15:50 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[3/7/2017 2:15:50 AM] Entering buildAllProgramEntries() for 16001 programs.

And then finally, here is the log from just a moment ago, when I did my manual SAVE+EXIT. Seems to be perfect. Note that there is a mention of the last update (i.e. last night's failed attempt first at 2AM and then re-scheduled at 2:15AM, "Last Run 3/7/2017 2:15:07 AM; Exit: 0x00041301". The error return code didn't actually appear on the log itself.

Code: Select all

[3/7/2017 2:15:32 PM] ===============================================================================
[3/7/2017 2:15:32 PM]  Activating the epg123 configuration GUI.
[3/7/2017 2:15:32 PM] ===============================================================================
[3/7/2017 2:15:33 PM] [ INFO] epg123 is up to date. version: 1.1.3
[3/7/2017 2:15:33 PM] [ INFO] Successfully queried the Task Scheduler for status. status: Ready. Last Run 3/7/2017 2:15:07 AM; Exit: 0x00041301.
[3/7/2017 2:15:33 PM] [ INFO] Token request successful. serverID: 20141201.web.3
[3/7/2017 2:15:34 PM] [ INFO] Status request successful. account expires: 2017-04-21T07:19:18Z , lineups: 2/4 , lastDataUpdate: 2017-03-07T22:00:52Z
[3/7/2017 2:15:34 PM] [ INFO] system status: Online , message: No known issues.
[3/7/2017 2:15:34 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[3/7/2017 2:15:34 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[3/7/2017 2:15:34 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[3/7/2017 2:15:44 PM] ===============================================================================
[3/7/2017 2:15:44 PM]  Beginning epg123 update execution.
[3/7/2017 2:15:44 PM] ===============================================================================
[3/7/2017 2:15:45 PM] [ INFO] Successfully retrieved TMDb configurations.
[3/7/2017 2:15:45 PM] [ INFO] epg123 version 1.1.3 , DaysToDownload: 28 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: True , AutoAddNew: True
[3/7/2017 2:15:45 PM] [ INFO] Token request successful. serverID: 20141201.web.3
[3/7/2017 2:15:45 PM] [ INFO] epg123 is up to date. version: 1.1.3
[3/7/2017 2:15:45 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[3/7/2017 2:15:45 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[3/7/2017 2:15:46 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[3/7/2017 2:15:46 PM] Entering getAllScheduleEntryMd5s() for 28 days on 84 stations.
[3/7/2017 2:15:48 PM] [ INFO] Successfully retrieved Md5s for 84 station's daily schedules.
[3/7/2017 2:15:51 PM] [ INFO] Successfully retrieved 84 station's daily schedules.
[3/7/2017 2:16:01 PM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[3/7/2017 2:16:01 PM] Entering buildAllProgramEntries() for 17080 programs.
[3/7/2017 2:16:42 PM] [ INFO] Successfully retrieved 2098 programs metadata.
[3/7/2017 2:16:50 PM] Exiting buildAllProgramEntries(). SUCCESS.
[3/7/2017 2:16:50 PM] Entering buildAllGenericSeriesInfoDescriptions() for 2265 series.
[3/7/2017 2:16:55 PM] [ INFO] Successfully retrieved 131 programs generic description metadata.
[3/7/2017 2:16:56 PM] Exiting buildAllGenericSeriesInfoDescriptions(). SUCCESS.
[3/7/2017 2:16:56 PM] Entering getAllMoviePosters() for 1784 movies.
[3/7/2017 2:16:56 PM] [ INFO] Successfully retrieved artwork info for 200 programs.
[3/7/2017 2:16:57 PM] [ INFO] TMDb catalog search for "American Jihad" from 2017 found 1 results.
[3/7/2017 2:16:57 PM] [ INFO] TMDb catalog search for "Forgotten Evil" from 2017 found 0 results.
[3/7/2017 2:16:58 PM] [ INFO] TMDb catalog search for "Forgotten Evil" from 2018 found 0 results.
[3/7/2017 2:16:58 PM] [ INFO] TMDb catalog search for "Forgotten Evil" from 2016 found 0 results.
[3/7/2017 2:16:58 PM] [ INFO] TMDb catalog search for "Daughter for Sale" from 2017 found 0 results.
[3/7/2017 2:16:58 PM] [ INFO] TMDb catalog search for "Daughter for Sale" from 2018 found 0 results.
[3/7/2017 2:16:58 PM] [ INFO] TMDb catalog search for "Daughter for Sale" from 2016 found 0 results.
[3/7/2017 2:16:58 PM] [ INFO] TMDb catalog search for "The Outlaw and His Wife" from 1917 found 0 results.
[3/7/2017 2:16:58 PM] [ INFO] TMDb catalog search for "The Outlaw and His Wife" from 1918 found 1 results.
[3/7/2017 2:16:58 PM] [ INFO] TMDb catalog search for "To Walk Invisible: The Brontë Sisters" from 2016 found 1 results.
[3/7/2017 2:16:58 PM] [ INFO] TMDb catalog search for "Return to Green Acres" from 1990 found 1 results.
[3/7/2017 2:16:58 PM] [ INFO] TMDb catalog search for "The Children of An Lac" from 1980 found 0 results.
[3/7/2017 2:16:59 PM] [ INFO] TMDb catalog search for "The Children of An Lac" from 1981 found 0 results.
[3/7/2017 2:16:59 PM] [ INFO] TMDb catalog search for "The Children of An Lac" from 1979 found 0 results.
[3/7/2017 2:16:59 PM] [ INFO] TMDb catalog search for "Sleeping Beauty" from 1987 found 1 results.
[3/7/2017 2:16:59 PM] [ INFO] TMDb catalog search for "The Belstone Fox" from 1973 found 1 results.
[3/7/2017 2:16:59 PM] [ INFO] TMDb catalog search for "Have You Seen My Son?" from 1996 found 0 results.
[3/7/2017 2:16:59 PM] [ INFO] TMDb catalog search for "Have You Seen My Son?" from 1997 found 0 results.
[3/7/2017 2:16:59 PM] [ INFO] TMDb catalog search for "Have You Seen My Son?" from 1995 found 0 results.
[3/7/2017 2:16:59 PM] [ INFO] TMDb catalog search for "Foxfire Light" from 1982 found 1 results.
[3/7/2017 2:16:59 PM] [ INFO] TMDb catalog search for "The Man From Button Willow" from 1965 found 1 results.
[3/7/2017 2:16:59 PM] [ INFO] TMDb catalog search for "Son-Rise: A Miracle of Love" from 1979 found 1 results.
[3/7/2017 2:17:00 PM] [ INFO] TMDb catalog search for "Twelve Angry Men" from 1957 found 1 results.
[3/7/2017 2:17:00 PM] Exiting getAllMoviePosters(). SUCCESS.
[3/7/2017 2:17:00 PM] Entering getAllSeriesImages() for 2265 series.
[3/7/2017 2:17:01 PM] [ INFO] Successfully retrieved artwork info for 430 programs.
[3/7/2017 2:17:02 PM] Exiting getAllSeriesImages(). SUCCESS.
[3/7/2017 2:17:02 PM] Entering writeMxf().
[3/7/2017 2:17:02 PM] Exiting writeMxf(). SUCCESS.
[3/7/2017 2:17:02 PM] Entering writeImageArchive().
[3/7/2017 2:17:02 PM] Exiting writeImageArchive(). SUCCESS.
[3/7/2017 2:17:05 PM] [ INFO] 2634 files deleted from the cache directory during cleanup.
[3/7/2017 2:17:05 PM] [STATS] Generated .mxf file contains 84 services, 2265 series, 17080 programs, and 33331 people with 3976 image links.
[3/7/2017 2:17:05 PM] ====================== Beginning epg123 client execution. =====================
[3/7/2017 2:17:05 PM] [ INFO] Import=True , Match=True , NoLogo=False
[3/7/2017 2:17:05 PM] [ INFO] import filename = epg123.mxf
[3/7/2017 2:17:37 PM] [ INFO] Successfully imported .mxf file into Media Center. Exit code: 0
[3/7/2017 2:17:39 PM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[3/7/2017 2:17:39 PM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[3/7/2017 2:17:39 PM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[3/7/2017 2:17:39 PM] [STATS] epg123Client mxf load and database reindex execution time was 00:00:33.9300002.
[3/7/2017 2:17:39 PM] ====================== Completed epg123 client execution. =====================
[3/7/2017 2:17:41 PM] [STATS] epg123 update execution time was 00:01:56.4852008.

[garyan2]

I can't even guess what happened at the 3/7 2AM run. The only things that happen after the third line ("=== ") is is reads in the epg123.cfg file and establishes a token with tmdb. Failure of either of these should have written something to the trace.log file. Is there anything in Event Viewer at that time?

The exit code logged for the 2:15 run of 0x00041301 is for the task itself, not epg123. The exit code means that at 2:15 the task scheduler thought there was already an instance of epg123 running. Do you have possibly 2 tasks in your scheduler?

[DSperber]

Well, once again tonight's 2AM update did NOT go well.

Code: Select all

[3/8/2017 2:00:00 AM] ===============================================================================
[3/8/2017 2:00:00 AM]  Beginning epg123 update execution.
[3/8/2017 2:00:00 AM] ===============================================================================
[3/8/2017 2:00:03 AM] [ INFO] Successfully retrieved TMDb configurations.
[3/8/2017 2:00:03 AM] [ INFO] epg123 version 1.1.3 , DaysToDownload: 28 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: True , AutoAddNew: True
[3/8/2017 2:00:07 AM] [ INFO] Token request successful. serverID: 20141201.web.3
[3/8/2017 2:00:08 AM] [ INFO] epg123 is up to date. version: 1.1.3
[3/8/2017 2:00:11 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[3/8/2017 2:00:12 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[3/8/2017 2:00:15 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[3/8/2017 2:00:15 AM] Entering getAllScheduleEntryMd5s() for 28 days on 84 stations.
[3/8/2017 2:01:16 AM] [ERROR] Did not receive a response from Schedules Direct for Md5s of 84 station's daily schedules.
[3/8/2017 2:01:16 AM] [ERROR] Problem occurred during getMd5ScheduleEntries(). Exiting.
[3/8/2017 2:01:16 AM] [ERROR] Failed to create MXF file. Exiting.
[3/8/2017 2:01:16 AM] [STATS] epg123 update execution time was 00:01:15.5460000.
[3/8/2017 2:01:16 AM] ====================== Beginning epg123 client execution. =====================
[3/8/2017 2:01:16 AM] [ INFO] Import=True , Match=True , NoLogo=False
[3/8/2017 2:01:16 AM] [ INFO] import filename = epg123.mxf
[3/8/2017 2:01:39 AM] [ INFO] Successfully imported .mxf file into Media Center. Exit code: 0
[3/8/2017 2:01:40 AM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[3/8/2017 2:01:40 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[3/8/2017 2:01:40 AM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[3/8/2017 2:01:40 AM] [STATS] epg123Client mxf load and database reindex execution time was 00:00:24.0475000.
[3/8/2017 2:01:40 AM] ====================== Completed epg123 client execution. =====================

I'm contemplating going back to v1.1.1, just to see if the nightly update returns to normal. Things have been working fine for at least a week, since completing the build of my second HTPC and not realizing I'd scheduled the new nightly update at 2AM and was still letting the original HTPC do it's nightly 2AM update as well. The fact that two updates to SD occurred at the same instant knocked one of them out, and that was pointed out to me by another forum member.

Once I changed my original HTPC to update at 1:30AM and the second HTPC to update at 2AM, everything on both machines went just fine.

So this latest problem seems strictly tied to the automatic nightly v1.1.3 update. If I manually SAVE+EXECUTE during the day it runs fine.

[Beaker1024]

Same issue here. I thought v1.1.3 was working ok (I upgraded same day it was released) but last two nights the scheduled updates (4am) don't work. I easily found this error in the Trace.log file.

Code: Select all

************************** March 7th **************************
[3/7/2017 4:00:04 AM] Entering getAllScheduleEntryMd5s() for 21 days on 346 stations.
[3/7/2017 4:01:05 AM] [ERROR] Did not receive a response from Schedules Direct for Md5s of 346 station's daily schedules.
[3/7/2017 4:01:05 AM] [ERROR] Problem occurred during getMd5ScheduleEntries(). Exiting.
[3/7/2017 4:01:05 AM] [ERROR] Failed to create MXF file. Exiting.
************************** March 8th **************************
[3/8/2017 4:00:11 AM] Entering getAllScheduleEntryMd5s() for 21 days on 346 stations.
[3/8/2017 4:01:12 AM] [ERROR] Did not receive a response from Schedules Direct for Md5s of 346 station's daily schedules.
[3/8/2017 4:01:12 AM] [ERROR] Problem occurred during getMd5ScheduleEntries(). Exiting.
[3/8/2017 4:01:12 AM] [ERROR] Failed to create MXF file. Exiting.
[3/8/2017 4:01:12 AM] [STATS] epg123 update execution time was 00:01:10.6540412.

This morning I ran: epg123.exe and did a "save & execute" and all looks good:

Code: Select all

[3/8/2017 8:05:51 AM] Entering getAllScheduleEntryMd5s() for 21 days on 346 stations.
[3/8/2017 8:05:58 AM] [ INFO] Successfully retrieved Md5s for 346 station's daily schedules.
[3/8/2017 8:06:05 AM] [ INFO] Successfully retrieved 346 station's daily schedules.
[3/8/2017 8:06:48 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.

Normally I'd caulk it up to an odd night for SD but it was the last two nights consistently same error for the task scheduler ran update while manual Save&execute works. Might be something to do with the scheduled ran update?

[garyan2]

Going back in epg123 versions won't help any. I suspect this is the AWS servers. Considering the timing, Amazon could be doing some serious maintenance and/or rebuilds. I checked late last night, and response was really slow and unpredictable. My update failed last night as well.

It is possible that I am getting invalid returns from SD, but they should be recorded in the trace.log file. I'll query Schedules Direct to see if they are aware of what is happening.

[Sammy2]

I'm still on 1.0.2 and was just about to report this for the last two nights' runs:

Code: Select all

[3/7/2017 12:00:01 AM] ===============================================================================
[3/7/2017 12:00:01 AM]  Beginning epg123 update execution.
[3/7/2017 12:00:01 AM] ===============================================================================
[3/7/2017 12:00:01 AM] [ INFO] epg123 version 1.0.2 , DaysToDownload: 30 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , AutoImport: True , TMDbCoverArt: True , LogoOverride: False , Automatch: True , AutoAddNew: True
[3/7/2017 12:00:02 AM] [ INFO] Successfully retrieved TMDb configurations.
[3/8/2017 12:00:00 AM] ===============================================================================
[3/8/2017 12:00:00 AM]  Beginning epg123 update execution.
[3/8/2017 12:00:00 AM] ===============================================================================
[3/8/2017 12:00:00 AM] [ INFO] epg123 version 1.0.2 , DaysToDownload: 30 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , AutoImport: True , TMDbCoverArt: True , LogoOverride: False , Automatch: True , AutoAddNew: True
[3/8/2017 12:00:00 AM] [ INFO] Successfully retrieved TMDb configurations.
[3/8/2017 12:00:11 AM] [ INFO] Token request successful. serverID: 20141201.web.3

I'm in process of a manual run right now and will report back when finished.

[12noon]

Going back in epg123 versions won't help any. I suspect this is the AWS servers. Considering the timing, Amazon could be doing some serious maintenance and/or rebuilds. I checked late last night, and response was really slow and unpredictable. My update failed last night as well.

It is possible that I am getting invalid returns from SD, but they should be recorded in the trace.log file. I'll query Schedules Direct to see if they are aware of what is happening.

I can confirm that AWS was experiencing issues last night (around midnight Central Time) because all of our Amazon Echoes were inoperable.

[Sammy2]

Rather than post the whole log, which shows success with no errors, I will just state that it ran without errors.

[Sammy2]

Going back in epg123 versions won't help any. I suspect this is the AWS servers. Considering the timing, Amazon could be doing some serious maintenance and/or rebuilds. I checked late last night, and response was really slow and unpredictable. My update failed last night as well.

It is possible that I am getting invalid returns from SD, but they should be recorded in the trace.log file. I'll query Schedules Direct to see if they are aware of what is happening.

I can confirm that AWS was experiencing issues last night (around midnight Central Time) because all of our Amazon Echoes were inoperable.

I'm glad my Home Automation is a VeraPlus which, while it can be reached remotely through a relay server, runs on our LAN without the necessity of phoning home. I prefer this much more than having to rely on someone else' server but it has it's drawbacks as well..

[garyan2]

I would also recommend everyone to possibly shift their scheduled update times. It appears we all tend to perform our updates at 12AM or 2AM local times ... doesn't help the servers when everyone attacks it at once. I don't know about everyone else, but my incremental updates only take about 2 minutes ... larger lineups will of course be longer.

I know it would annoy a lot of our senses for order with an update time of say 1:37AM, but it will be easier on the servers and increase likelyhood of success.

[Sammy2]

I would also recommend everyone to possibly shift their scheduled update times. It appears we all tend to perform out updates at 12AM or 2AM local times ... doesn't help the servers when everyone attacks it at once. I don't know about everyone else, but my incremental updates only take about 2 minutes ... larger lineups will of course be longer.

I know it would annoy a lot of our senses for order with an update time of say 1:37AM, but it will be easier on the servers and increase likelyhood of success.

Good point. And don't chose 1:37 AM either!

I will do this today. I suspect it must be changed in the task manager. The manual update I just did was completed in under 3 minutes and I have a couple hundred stations. Is there any harm in running the update while WMC is in use for viewing? I'm thinking of setting it for sometime during the day when viewing is unlikely but possible.

[garyan2]

I would also recommend everyone to possibly shift their scheduled update times. It appears we all tend to perform out updates at 12AM or 2AM local times ... doesn't help the servers when everyone attacks it at once. I don't know about everyone else, but my incremental updates only take about 2 minutes ... larger lineups will of course be longer.

I know it would annoy a lot of our senses for order with an update time of say 1:37AM, but it will be easier on the servers and increase likelyhood of success.

Good point. And don't chose 1:37 AM either!

I will do this today. I suspect it must be changed in the task manager. The manual update I just did was completed in under 3 minutes and I have a couple hundred stations. Is there any harm in running the update while WMC is in use for viewing? I'm thinking of setting it for sometime during the day when viewing is unlikely but possible.

I haven't had any problems running updates while watching TV, but I haven't tested that out a lot. Keep in mind, I will abort an update if a recording is in progress.

[stuartm]

I did encounter a problem running an update while watching TV. It left my tuners in a state such that the tuners were not available the next time I tried to use them until I did a system reboot.
I suppose it could have been a coincidence since I haven't tried it again to see if it happens every time. (This was my Prime cable tuners).
So I am just avoiding running updates during times I would be watching TV.

[Sammy2]

I haven't had the time to change the schedule yet but last night's run didn't go too well.

Code: Select all

[3/9/2017 12:00:00 AM] ===============================================================================
[3/9/2017 12:00:00 AM]  Beginning epg123 update execution.
[3/9/2017 12:00:00 AM] ===============================================================================
[3/9/2017 12:00:00 AM] [ INFO] epg123 version 1.0.2 , DaysToDownload: 30 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , AutoImport: True , TMDbCoverArt: True , LogoOverride: False , Automatch: True , AutoAddNew: True
[3/9/2017 12:00:00 AM] [ INFO] Successfully retrieved TMDb configurations.
[3/9/2017 12:00:05 AM] [ INFO] Token request successful. serverID: 20141201.web.3
[3/9/2017 12:00:10 AM] [ INFO] epg123 is not up to date. Latest version is 1.1.3 and can be downloaded from http://epg123.garyan2.net.
[3/9/2017 12:00:15 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[3/9/2017 12:00:23 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA04768-X.
[3/9/2017 12:00:24 AM] Entering getAllScheduleEntryMd5s() for 30 days on 442 stations.
[3/9/2017 12:02:24 AM] [ERROR] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
[3/9/2017 12:02:24 AM] [ INFO] Changing timeout to 240 seconds and trying again.
[3/9/2017 12:06:24 AM] [ERROR] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
[3/9/2017 12:06:24 AM] [ INFO] Changing timeout to 360 seconds and trying again.

[rkulagow]

I've added additional servers to the pool and will continue to monitor the load once the "catch-up" surge dissipates.

[Sammy2]

I've added additional servers to the pool and will continue to monitor the load once the "catch-up" surge dissipates.

Thanks, Robert.

I had a successful manual run that took 9 minutes about an hour ago. I need to change that download time to a different time..

[Sammy2]

What about clicking the Random Delay check box? Will that make it run at different times such that it doesn't overload the servers? TIA

[garyan2]

What about clicking the Random Delay check box? Will that make it run at different times such that it doesn't overload the servers? TIA

epg123 task.JPG

Certainly an option. I didn't pursue this a long time ago since most of us are control freaks and if we want epg123 to run at 0200, then gosh durnit, it should run at 0200. (am I projecting?)

If implemented, it would definitely need to be something the server/client topography users would need to take into account. Those that have multiple stand-alone updates would also need to be aware to avoid overlapping times.

[Sammy2]

What about clicking the Random Delay check box? Will that make it run at different times such that it doesn't overload the servers? TIA

epg123 task.JPG

Certainly an option. I didn't pursue this a long time ago since most of us are control freaks and if we want epg123 to run at 0200, then gosh durnit, it should run at 0200. (am I projecting?)

If implemented, it would definitely need to be something the server/client topography users would need to take into account. Those that have multiple stand-alone updates would also need to be aware to avoid overlapping times.

So people like me, with simple set ups (mainly do to DRM and not having a Server/Client topography), could or maybe even SHOULD, click the box?

[garyan2]

It wouldn't harm anything and only benefit the community as a whole. May even help reduce the number of servers SD needs to meet demand... a win/win.