EPG123 Bug Reports

An evolving, supported alternative to Rovi
Important Information
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf

Re: Servers Overloaded?

Post#521 » Fri Mar 10, 2017 6:43 am

epg123 worked for me up to March 4, bit since Mar 5 I get this:

Code: Select all
3/5/2017 2:00:00 AM] ===============================================================================
[3/5/2017 2:00:00 AM]  Beginning epg123 update execution.
[3/5/2017 2:00:00 AM] ===============================================================================
[3/5/2017 2:00:01 AM] [ INFO] Successfully retrieved TMDb configurations.
[3/5/2017 2:00:01 AM] [ INFO] epg123 version 1.1.3 , DaysToDownload: 21 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: True , AutoAddNew: True
[3/5/2017 2:00:04 AM] [ INFO] Token request successful. serverID: 20141201.web.3
[3/5/2017 2:00:05 AM] [ INFO] epg123 is up to date. version: 1.1.3
[3/5/2017 2:00:07 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[3/5/2017 2:00:12 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA65194-X.
[3/5/2017 2:00:13 AM] Entering getAllScheduleEntryMd5s() for 21 days on 744 stations.
[3/5/2017 2:01:15 AM] [ERROR] Did not receive a response from Schedules Direct for Md5s of 744 station's daily schedules.
[3/5/2017 2:01:15 AM] [ERROR] Problem occurred during getMd5ScheduleEntries(). Exiting.
[3/5/2017 2:01:15 AM] [ERROR] Failed to create MXF file. Exiting.
[3/5/2017 2:01:15 AM] [STATS] epg123 update execution time was 00:01:15.4173136.


I think I updated from 1.1.2 to 1.1.3 on the 4th as well - just unzipped the newer version over the old.
tomuo
 
Posts: 6
Joined: 13 August 2015
Location: Los Angeles
HTPC Specs: Show details

Post#522 » Fri Mar 10, 2017 7:07 am

tomuo wrote:epg123 worked for me up to March 4, bit since Mar 5 I get this:

I think I updated from 1.1.2 to 1.1.3 on the 4th as well - just unzipped the newer version over the old.

The 0200 update time appears to be very popular ... try changing the update time and throwing in some odd number of minutes so as to not be on the hour.

The Amazon servers haven't been in the best of health lately. Also, SD has put online some more microservers to help out with the workload. Those 2 things combined should make the updates successful. Also note that any manual updates during the day rarely ever fail.

Your update from 1.1.2 to 1.1.3 was fine. No concern on your side.
User avatar
garyan2
 
Posts: 1465
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#523 » Fri Mar 10, 2017 8:20 am

It might be a good idea for the server to return a "BUSY - retry in x seconds" response based on the current system load, then the client can wait that amount of time and try again.

I guess the client can do that anyway without the BUSY mechanism if you get a timeout, but then you may just be contributing to the problem by "spamming", but you can use an exponential back-off to alleviate that.
Space
 
Posts: 942
Joined: 2 June 2013

Post#524 » Fri Mar 10, 2017 2:32 pm

Space wrote:It might be a good idea for the server to return a "BUSY - retry in x seconds" response based on the current system load, then the client can wait that amount of time and try again.

I guess the client can do that anyway without the BUSY mechanism if you get a timeout, but then you may just be contributing to the problem by "spamming", but you can use an exponential back-off to alleviate that.

SD actually does return a "retry" time when the servers are busy... it is currently being ignored, but should of at least been reported. Maybe that is where the strangeness in updates recently is coming from.
User avatar
garyan2
 
Posts: 1465
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#525 » Wed Mar 15, 2017 3:07 pm

garyan2 wrote:
tomuo wrote:epg123 worked for me up to March 4, bit since Mar 5 I get this:

I think I updated from 1.1.2 to 1.1.3 on the 4th as well - just unzipped the newer version over the old.

The 0200 update time appears to be very popular ... try changing the update time and throwing in some odd number of minutes so as to not be on the hour.

The Amazon servers haven't been in the best of health lately. Also, SD has put online some more microservers to help out with the workload. Those 2 things combined should make the updates successful. Also note that any manual updates during the day rarely ever fail.

Your update from 1.1.2 to 1.1.3 was fine. No concern on your side.


Update - thanks, no errors since the scheduled run on the 10th. I would like to change the update time - but it's greyed out in the UI. What needs to be disabled to let me change this and store a new auto-update?
tomuo
 
Posts: 6
Joined: 13 August 2015
Location: Los Angeles
HTPC Specs: Show details

Post#526 » Wed Mar 15, 2017 3:44 pm

tomuo wrote:Update - thanks, no errors since the scheduled run on the 10th. I would like to change the update time - but it's greyed out in the UI. What needs to be disabled to let me change this and store a new auto-update?

You just need to delete the current task and create a new one with the new time.
User avatar
garyan2
 
Posts: 1465
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#527 » Thu Mar 16, 2017 4:27 am

garyan2 wrote:
tomuo wrote:Update - thanks, no errors since the scheduled run on the 10th. I would like to change the update time - but it's greyed out in the UI. What needs to be disabled to let me change this and store a new auto-update?

You just need to delete the current task and create a new one with the new time.


Hmm, pressing the Delete button didn't do anything the first 3 or 4 times I tried it. 5th time it un-greyed the fields to put in the time for the new task.
Only got an entry in the log when it succeeded

Code: Select all
[3/15/2017 9:22:56 PM] [ INFO] Successfully deleted the daily update task from Task Scheduler.
[3/15/2017 9:22:56 PM] [ INFO] Successfully queried the Task Scheduler for status. status: No task is scheduled to run..
[3/15/2017 9:23:29 PM] [ INFO] Successfully created the daily update task in Task Scheduler for 05:15.
[3/15/2017 9:23:29 PM] [ INFO] Successfully queried the Task Scheduler for status. status: Ready.The task has not yet run. Exit: 0x00000001.
tomuo
 
Posts: 6
Joined: 13 August 2015
Location: Los Angeles
HTPC Specs: Show details

Post#528 » Thu Apr 06, 2017 7:15 pm

So lately, with nothing else changing on my HTPC (homerun Prime 6cc) setup other than the recent EPG123 updates, I have been losing a tuner (tuner not found) every night at around 10-11PM. Is it possible this is EPG123 related or it really can't be and therefore I should get in contact with SiliconDust to get their help troubleshooting?

For some more information, I have two multi-stream cards and so I can record up to 6 shows. At around 10-11PM I'll start getting thrown the WMC (Windows 7) failure to record errors (that popup in the bottom right task bar). When I check the HDHomeRun setup application it shows that one card is active and the other can't be found. When I click on the missing card (to go to its IP address) it fails to load in the browser. The only fix is to turn off and turn back on my HDHomeRun box. Then both cards are seen again and all 6 streams can be used. I did it last night and just now (noon) I set my WMC to record 6 shows and it did so no problem. But for whatever reason come 10-11PM tonight it will most likely lose a card/tuner.

This has never happened to me before, any clue what is going on?
NathanP2007
 
Posts: 19
Joined: 12 June 2016

Post#529 » Thu Apr 06, 2017 8:22 pm

When is your scheduled guide updates? There has been discussion that if a tuner is in use during the import, it not be released properly so no longer available.

I'm not sure how this theory holds up with the HDHomerun software not being able to see it either, though.

Sent from my LGLS775 using Tapatalk
User avatar
garyan2
 
Posts: 1465
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#530 » Thu Apr 06, 2017 8:53 pm

Pretty unlikely this is a EPG123 problem if you need to power cycle your Prime to get it back. More likely a Prime firmware or power supply problem or possibly one of your cable cards is failing. I would go over to the SiliconDust forum and ask for help or open a trouble ticket with SD.
stuartm
 
Posts: 230
Joined: 5 November 2012
Location: Longmont, CO
HTPC Specs: Show details

Post#531 » Sat Apr 08, 2017 12:34 am

NathanP2007 wrote:So lately, with nothing else changing on my HTPC (homerun Prime 6cc) setup other than the recent EPG123 updates, I have been losing a tuner (tuner not found) every night at around 10-11PM. Is it possible this is EPG123 related or it really can't be and therefore I should get in contact with SiliconDust to get their help troubleshooting?


Do you happen to have your Primes using DHCP and renewing at that time? Check this entry over on the emby forum for something that may be related. https://emby.media/community/index.php? ... ntry432951
User avatar
garyan2
 
Posts: 1465
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#532 » Sat Apr 08, 2017 12:54 am

garyan2 wrote:
NathanP2007 wrote:So lately, with nothing else changing on my HTPC (homerun Prime 6cc) setup other than the recent EPG123 updates, I have been losing a tuner (tuner not found) every night at around 10-11PM. Is it possible this is EPG123 related or it really can't be and therefore I should get in contact with SiliconDust to get their help troubleshooting?


Do you happen to have your Primes using DHCP and renewing at that time? Check this entry over on the emby forum for something that may be related. https://emby.media/community/index.php? ... ntry432951


I don't know if it uses DHCP, do you know how I can find out? Wouldn't it be odd that I'd be having that issue all of a sudden when my router, switch and everything else about my network is the same as it has been for years? I put in a ticket with SiliconDust and they got back to me. When I have the issue again I'll send them the diagnostic info they asked for. Hopefully it is a dying cable card or something simple to fix.
NathanP2007
 
Posts: 19
Joined: 12 June 2016

Post#533 » Sat Apr 08, 2017 2:22 am

You're pretty much guaranteed to be using DHCP. The question is really if your DHCP server only leases for 24 hours and renews around 10PM for your primes.
User avatar
garyan2
 
Posts: 1465
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#534 » Sun Apr 16, 2017 1:46 pm

Failure to run. Consistently fails today when retrying. Does the same on either v1.1.3 or 1.1.4. Removed the cache and tried an empty cache run to rebuild. Still the same. Yesterday's run worked. Friday's run failed because of the SD problems.

Code: Select all
[4/16/2017 6:00:01 AM] ===============================================================================
[4/16/2017 6:00:01 AM]  Beginning epg123 update execution.
[4/16/2017 6:00:01 AM] ===============================================================================
[4/16/2017 6:00:02 AM] [ INFO] Successfully retrieved TMDb configurations.
[4/16/2017 6:00:02 AM] [ INFO] epg123 version 1.1.3 , DaysToDownload: 14 , PrefixEpisodeTitle: False , AppendEpisodeDesc: True , TMDbCoverArt: False , LogoOverride: False , AutoAddNew: True
[4/16/2017 6:00:03 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[4/16/2017 6:00:03 AM] [ INFO] epg123 is not up to date. Latest version is 1.1.4 and can be downloaded from http://epg123.garyan2.net.
[4/16/2017 6:00:04 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[4/16/2017 6:00:04 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-XXXXXXX-X.
[4/16/2017 6:00:05 AM] Entering getAllScheduleEntryMd5s() for 14 days on 585 stations.
[4/16/2017 6:00:08 AM] [ INFO] Successfully retrieved Md5s for 585 station's daily schedules.
[4/16/2017 6:00:27 AM] [ALERT] Failed to parse the schedule Md5 return for stationId 61854 (GOLFHD) on 2017-04-16 and after.
[4/16/2017 6:00:38 AM] [ INFO] Successfully retrieved 557 station's daily schedules.
[4/16/2017 6:01:00 AM] [ERROR] Did not find expected Md5Schedule file in cache directory.
[4/16/2017 6:01:00 AM] [ERROR] Problem occurred during processMd5ScheduleEntry().
[4/16/2017 6:01:00 AM] [ERROR] Failed to create MXF file. Exiting.
[4/16/2017 6:01:00 AM] [STATS] epg123 update execution time was 00:00:58.9497434.
glorp
 
Posts: 299
Joined: 23 September 2012

Post#535 » Sun Apr 16, 2017 2:49 pm

Having some more SD problems ... probably "aftershocks" from earlier problems. I submitted a ticket last night when I noticed it and it will probably be resolved soon.
User avatar
garyan2
 
Posts: 1465
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#536 » Mon Apr 17, 2017 12:49 am

All of a sudden the EPG is getting a message that my lineup is excluded from downloading and processing. I've have tried logging into SD directly and removing and re-adding my desired line up but still get the same message here is my trace file: Any suggestions would be greatly appreciated.
Thanks

[4/16/2017 8:29:37 PM] ===============================================================================
[4/16/2017 8:29:37 PM] Activating the epg123 configuration GUI.
[4/16/2017 8:29:37 PM] ===============================================================================
[4/16/2017 8:29:38 PM] [ INFO] epg123 is up to date. version: 1.1.4
[4/16/2017 8:29:38 PM] [ INFO] Successfully queried the Task Scheduler for status. status: No task is scheduled to run..
[4/16/2017 8:29:38 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[4/16/2017 8:29:38 PM] [ INFO] Status request successful. account expires: 2017-07-12T01:03:16Z , lineups: 1/4 , lastDataUpdate: 2017-04-16T16:32:08Z
[4/16/2017 8:29:38 PM] [ INFO] system status: Online , message: No known issues.
[4/16/2017 8:29:38 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[4/16/2017 8:29:38 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-MI02206-X.
[4/16/2017 8:30:07 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[4/16/2017 8:30:12 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[4/16/2017 8:30:17 PM] [ INFO] Successfully retrieved the headends for USA and postal code XXXXX.
[4/16/2017 8:30:21 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[4/16/2017 8:30:22 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-MI02206-X.
[4/16/2017 8:30:24 PM] ===============================================================================
[4/16/2017 8:30:24 PM] Beginning epg123 update execution.
[4/16/2017 8:30:24 PM] ===============================================================================
[4/16/2017 8:30:24 PM] [ INFO] Successfully retrieved TMDb configurations.
[4/16/2017 8:30:24 PM] [ INFO] epg123 version 1.1.4 , DaysToDownload: 14 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: True , AutoAddNew: True
[4/16/2017 8:30:24 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[4/16/2017 8:30:24 PM] [ INFO] epg123 is up to date. version: 1.1.4
[4/16/2017 8:30:24 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[4/16/2017 8:30:24 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-MI02206-X.
[4/16/2017 8:30:24 PM] [ INFO] Lineup USA-MI02206-X has been excluded from download and processing.
[4/16/2017 8:30:24 PM] Entering getAllScheduleEntryMd5s() for 14 days on 0 stations.
[4/16/2017 8:30:24 PM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[4/16/2017 8:30:24 PM] Entering buildAllProgramEntries() for 0 programs.
[4/16/2017 8:30:24 PM] Exiting buildAllProgramEntries(). SUCCESS.
[4/16/2017 8:30:24 PM] Entering buildAllGenericSeriesInfoDescriptions() for 0 series.
[4/16/2017 8:30:24 PM] Exiting buildAllGenericSeriesInfoDescriptions(). SUCCESS.
[4/16/2017 8:30:24 PM] Entering getAllMoviePosters() for 0 movies.
[4/16/2017 8:30:24 PM] Exiting getAllMoviePosters(). SUCCESS.
[4/16/2017 8:30:24 PM] Entering getAllSeriesImages() for 0 series.
[4/16/2017 8:30:24 PM] Exiting getAllSeriesImages(). SUCCESS.
[4/16/2017 8:30:24 PM] Entering writeMxf().
[4/16/2017 8:30:24 PM] Exiting writeMxf(). SUCCESS.
[4/16/2017 8:30:24 PM] Entering writeImageArchive().
[4/16/2017 8:30:24 PM] Exiting writeImageArchive(). SUCCESS.
[4/16/2017 8:30:24 PM] [ INFO] 0 files deleted from the cache directory during cleanup.
[4/16/2017 8:30:24 PM] [STATS] Generated .mxf file contains 0 services, 0 series, 0 programs, and 0 people with 0 image links.
[4/16/2017 8:30:24 PM] ====================== Beginning epg123 client execution. =====================
[4/16/2017 8:30:24 PM] [ INFO] Import=True , Match=True , NoLogo=False
[4/16/2017 8:30:25 PM] [ INFO] import filename = epg123.mxf
[4/16/2017 8:30:25 PM] [ INFO] Successfully imported .mxf file into Media Center. Exit code: 0
[4/16/2017 8:30:27 PM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[4/16/2017 8:30:27 PM] [ INFO] INFO: scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot" is currently running.
[4/16/2017 8:30:27 PM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[4/16/2017 8:30:27 PM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[4/16/2017 8:30:27 PM] [STATS] epg123Client mxf load and database reindex execution time was 00:00:02.7011545.
[4/16/2017 8:30:27 PM] ====================== Completed epg123 client execution. =====================
[4/16/2017 8:30:29 PM] [STATS] epg123 update execution time was 00:00:05.7293277.
Last edited by twos50 on Mon Apr 17, 2017 12:54 am, edited 1 time in total.
twos50
 
Posts: 4
Joined: 16 October 2012

Post#537 » Mon Apr 17, 2017 12:54 am

The schedules direct website only handles the XML server, not the JSON server epg123 uses.

In the epg123 GUI, in the top left corner of the lineup tab, you will see a red dot (stoplight). Click that and select the 'Include' menu item to change the button to green.
User avatar
garyan2
 
Posts: 1465
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#538 » Mon Apr 17, 2017 12:58 am

Thanks for the quick response garyan, but now i get:

===============================================================================
[4/16/2017 8:55:41 PM] Activating the epg123 configuration GUI.
[4/16/2017 8:55:41 PM] ===============================================================================
[4/16/2017 8:55:41 PM] [ INFO] epg123 is up to date. version: 1.1.4
[4/16/2017 8:55:41 PM] [ INFO] Successfully queried the Task Scheduler for status. status: No task is scheduled to run..
[4/16/2017 8:55:42 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[4/16/2017 8:55:42 PM] [ INFO] Status request successful. account expires: 2017-07-12T01:03:16Z , lineups: 1/4 , lastDataUpdate: 2017-04-17T00:29:56Z
[4/16/2017 8:55:42 PM] [ INFO] system status: Online , message: No known issues.
[4/16/2017 8:55:42 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[4/16/2017 8:55:42 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-MI02206-X.
[4/16/2017 8:56:09 PM] ===============================================================================
[4/16/2017 8:56:09 PM] Beginning epg123 update execution.
[4/16/2017 8:56:09 PM] ===============================================================================
[4/16/2017 8:56:09 PM] [ INFO] Successfully retrieved TMDb configurations.
[4/16/2017 8:56:09 PM] [ INFO] epg123 version 1.1.4 , DaysToDownload: 14 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: True , AutoAddNew: True
[4/16/2017 8:56:09 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[4/16/2017 8:56:09 PM] [ INFO] epg123 is up to date. version: 1.1.4
[4/16/2017 8:56:09 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[4/16/2017 8:56:09 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-MI02206-X.
[4/16/2017 8:56:09 PM] Entering getAllScheduleEntryMd5s() for 14 days on 504 stations.
[4/16/2017 8:56:12 PM] [ INFO] Successfully retrieved Md5s for 504 station's daily schedules.
[4/16/2017 8:56:24 PM] [ INFO] Successfully retrieved 504 station's daily schedules.
[4/16/2017 8:56:29 PM] [ERROR] Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.String[]' because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List<T>) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path '[2582].programs[18].videoProperties.0', line 1, position 13437471.
[4/16/2017 8:56:29 PM] [ERROR] Problem occurred during getMd5ScheduleEntries(). Exiting.
[4/16/2017 8:56:29 PM] [ERROR] Failed to create MXF file. Exiting.
[4/16/2017 8:56:29 PM] [STATS] epg123 update execution time was 00:00:20.2191565.
twos50
 
Posts: 4
Joined: 16 October 2012

Post#539 » Mon Apr 17, 2017 1:01 am

Yup, this issue popped up today and we're trying to track it down. It does however stop you from being able to update your guide data until it's fixed.
User avatar
garyan2
 
Posts: 1465
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#540 » Mon Apr 17, 2017 1:07 am

oh how is that, I has since cleard my cache. I haven't cleaned or rebuilt my database. I get no channels are available message in WMC..

PLease explain again if you have already done so.

Thanks much.

UPDATE:: Sorry I thought you said it DOESNT stop me from updating. Disregard the above if it does stop me from updating
twos50
 
Posts: 4
Joined: 16 October 2012

Previous

Return to EPG123



Who is online

Users browsing this forum: No registered users and 1 guest

cron