Schedules Direct Broke?
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: 173
- Joined: Mon Feb 03, 2014 1:03 am
- Location:
- HTPC Specs:
Status update in the 1st post here: https://forums.schedulesdirect.org/view ... =18&t=3201
now show "Service was re-enabled", but then has another note that "Lambda concurrency limit reached; request made to increase concurrent execution limits."
... and the SD website [ https://www.schedulesdirect.org/ ] still shows "SD_JSON Server offline for maintenance"
So I suspect they're still working this issue. I'm just going to wait until my normal overnight update and see if I have a GREEN EPG icon tomorrow.
now show "Service was re-enabled", but then has another note that "Lambda concurrency limit reached; request made to increase concurrent execution limits."
... and the SD website [ https://www.schedulesdirect.org/ ] still shows "SD_JSON Server offline for maintenance"
So I suspect they're still working this issue. I'm just going to wait until my normal overnight update and see if I have a GREEN EPG icon tomorrow.
- garyan2
- Posts: 7474
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
All,
I am probably going to release a newer version today. I would like to wait until the SD servers are back up before doing so but it isn't necessary. Maybe I'll make it a pre-release version....
I've added a custom log viewer which will color code the entries to maybe help folks read what is important when trying to troubleshoot.
In the last release when adjusting the timeout for getting a token, I had forgotten the timeout for the proxy/cache service.
I've adjusted the maximum request from EPG123 to SD from 5000 to 1000 for programs/schedules and 500 to 100 for image links/series descriptions. Maybe this will help the SD servers a little to be more successful. I'm concerned about the 29 second timeout on their end that will terminate a connection if the request hasn't been completed yet.
I am probably going to release a newer version today. I would like to wait until the SD servers are back up before doing so but it isn't necessary. Maybe I'll make it a pre-release version....
I've added a custom log viewer which will color code the entries to maybe help folks read what is important when trying to troubleshoot.
In the last release when adjusting the timeout for getting a token, I had forgotten the timeout for the proxy/cache service.
I've adjusted the maximum request from EPG123 to SD from 5000 to 1000 for programs/schedules and 500 to 100 for image links/series descriptions. Maybe this will help the SD servers a little to be more successful. I'm concerned about the 29 second timeout on their end that will terminate a connection if the request hasn't been completed yet.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 42
- Joined: Wed Jun 21, 2017 8:45 pm
- Location:
- HTPC Specs:
FWIW, I rolled back to 1.7.1.4, and now I'm just getting the "did not receive a response from Schedules Direct" and "failed to retrieve a token from Schedules Direct" errors, so I don't think there's anything wrong with my setup. Now just waiting on SD to figure things out!
-
- Posts: 34
- Joined: Tue Jul 28, 2015 12:26 pm
- Location:
- HTPC Specs:
Could this be residual problems from a Log4J vulnerability exploit?
-
- Posts: 151
- Joined: Wed Feb 25, 2015 2:38 am
- Location:
- HTPC Specs:
I was able to get my guide updated thru Jun 8th using V1.7.1.6. but there was some error. The icon was yellow but when I tried to view the log file I got an exception from the net framework and then the icon disappears until I reboot.
But at least I got it updated!
But at least I got it updated!
- garyan2
- Posts: 7474
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
Somewhere in your log file, you have an empty line. I'll get a catch in there to prevent the exception. Have you happened to have used hdhr2mxf in the past? That is actually how I managed to find this one. Even though notepad shows everything is good, if I open the log file in notepad++ I see empty separation lines and got the exceptions.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
- garyan2
- Posts: 7474
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
Released 1.7.1.7. See if that takes care of the exception. BTW: you don't have to reboot to get the tray application back. You just need to execute "c:\program files (x86)\epg123\epgtray.exe" to start it again.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 173
- Joined: Mon Feb 03, 2014 1:03 am
- Location:
- HTPC Specs:
Well, I'm still up so I decided to update to the latest (1.7.1.7) and do a manual update.
But it does the same thing I was seeing before: an immediate "Message Server offline for maintenance. Response: SERVER_OFFLINE" message.
So clearly SD is still broke. Checked the status updates in the 1st post of the thread r.e. the migration, and it now shows:
-----------------------------
2022-05-23T04:00Z - Service is being migrated back to existing PHP API until root cause of failure to obtain read handle against database can be determined. Python backend placed into offline mode.
2022-05-23T04:20Z - PHP API updating per normal daily update; when PHP service has 'caught up' to 3 days of non-updates, it will be placed back into service.
-----------------------------
So clearly they're going to be offline for a while while they roll back to the PHP setup and catch up to the updates. Hopefully all will be well tomorrow
But it does the same thing I was seeing before: an immediate "Message Server offline for maintenance. Response: SERVER_OFFLINE" message.
So clearly SD is still broke. Checked the status updates in the 1st post of the thread r.e. the migration, and it now shows:
-----------------------------
2022-05-23T04:00Z - Service is being migrated back to existing PHP API until root cause of failure to obtain read handle against database can be determined. Python backend placed into offline mode.
2022-05-23T04:20Z - PHP API updating per normal daily update; when PHP service has 'caught up' to 3 days of non-updates, it will be placed back into service.
-----------------------------
So clearly they're going to be offline for a while while they roll back to the PHP setup and catch up to the updates. Hopefully all will be well tomorrow
-
- Posts: 77
- Joined: Tue Mar 03, 2015 4:49 pm
- Location:
- HTPC Specs:
My overnight updated (03:49 BST using v1.7.1.5) appears to have worked, but with numerous warnings in the log file. It seems to have successfully populated another week of TV schedules.
-
- Posts: 173
- Joined: Mon Feb 03, 2014 1:03 am
- Location:
- HTPC Specs:
Well, I was STILL up (I'm a night owl, but this is late even for me) ... so I checked and saw the SD status said they were back up.
So I ran a manual update ... and Voila !! Nice GREEN EPG icon
Hopefully this doesn't repeat in the next week or so when SD decides to do the migration again
So I ran a manual update ... and Voila !! Nice GREEN EPG icon
Hopefully this doesn't repeat in the next week or so when SD decides to do the migration again
-
- Posts: 77
- Joined: Tue Mar 03, 2015 4:49 pm
- Location:
- HTPC Specs:
I have just tried a manual update using v1.7.1.7 and it completed successfully with no warnings. However, it took 14 minutes!
-
- Posts: 42
- Joined: Wed Jun 21, 2017 8:45 pm
- Location:
- HTPC Specs:
I see that SD migrated back to the old servers until they can figure out what's wrong.
I installed 1.7.1.7, and I got the same error I was getting with 1.7.1.5: [ERROR] Unhandled exception caught from epg123.exe. message: The requested security protocol is not supported.
I rolled back to 1.7.1.4, and I was still getting the "did not receive a response from Schedules Direct" and "failed to retrieve token from Schedules Direct." So back to 1.7.1.7 and the "security protocol" error.
Is 1.7.1.7 working for everyone else? I'm puzzled as to why it's not working for me.
I installed 1.7.1.7, and I got the same error I was getting with 1.7.1.5: [ERROR] Unhandled exception caught from epg123.exe. message: The requested security protocol is not supported.
I rolled back to 1.7.1.4, and I was still getting the "did not receive a response from Schedules Direct" and "failed to retrieve token from Schedules Direct." So back to 1.7.1.7 and the "security protocol" error.
Is 1.7.1.7 working for everyone else? I'm puzzled as to why it's not working for me.
-
- Posts: 38
- Joined: Sat Dec 30, 2017 8:08 pm
- Location:
- HTPC Specs:
After 3 days of connection refusal from SD - as a result of their upgrading and regression - I have a full update today at 1333 GMT+1
-
- Posts: 42
- Joined: Wed Jun 21, 2017 8:45 pm
- Location:
- HTPC Specs:
I've been trying various versions, and no luck with any of them. I went back to 1.7.0.12, the version I was using until a few days ago, and I'm getting these errors:
[ERROR] There are 0 stations queued for download from 1 subscribed lineup. Exiting.
[ERROR] Check that lineups are 'INCLUDED' and stations are selected in the EPG123 GUI.
[ERROR] Failed to create MXF file. Exiting.
EDIT: I think I figured this out, and reselected my lineup. But It's still now downloading anything.
[ERROR] There are 0 stations queued for download from 1 subscribed lineup. Exiting.
[ERROR] Check that lineups are 'INCLUDED' and stations are selected in the EPG123 GUI.
[ERROR] Failed to create MXF file. Exiting.
EDIT: I think I figured this out, and reselected my lineup. But It's still now downloading anything.
Last edited by mainertodd on Mon May 23, 2022 1:28 pm, edited 1 time in total.
-
- Posts: 151
- Joined: Wed Feb 25, 2015 2:38 am
- Location:
- HTPC Specs:
It appears SD has finally got it together. Thanks for the updates Gary!
-
- Posts: 42
- Joined: Wed Jun 21, 2017 8:45 pm
- Location:
- HTPC Specs:
Well, I'm stumped. I've tried uninstalling and reinstalling, rebuilding the WMC database, running the Client Setup again. Nothing is working on any version of the program--it won't download the data no matter what I do.
EDIT: argh, finally. I don't know what did the trick, but I finally got it to work properly on 1.7.1.4. It ran an update and added another couple days of guide data (through Saturday the 11th). I tried running another manual update just to be sure, and it worked.
EDIT: argh, finally. I don't know what did the trick, but I finally got it to work properly on 1.7.1.4. It ran an update and added another couple days of guide data (through Saturday the 11th). I tried running another manual update just to be sure, and it worked.
Last edited by mainertodd on Mon May 23, 2022 2:03 pm, edited 1 time in total.
-
- Posts: 17
- Joined: Tue Jul 05, 2011 6:56 pm
- Location:
- HTPC Specs:
1.7.1.5 was still failing for me today so I updated to 1.7.1.7 and it ran fine.
- garyan2
- Posts: 7474
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
All,
I elevated 1.7.1.7 to full release. The timeout period for 1.7.1.5 was too short for trying to download from the "old" server. I had changed the timeouts for downloading everything but the token and user status back to 5 minutes rather than 30 seconds. This should get everyone happy again.
I elevated 1.7.1.7 to full release. The timeout period for 1.7.1.5 was too short for trying to download from the "old" server. I had changed the timeouts for downloading everything but the token and user status back to 5 minutes rather than 30 seconds. This should get everyone happy again.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 104
- Joined: Tue Jun 14, 2016 11:44 pm
- Location:
- HTPC Specs:
I downloaded 1.7.1.7 when it was still reading 'beta'. Perhaps 30 minutes before Garyan2 note that it was elevated. Do I need to download again?
Meanwhile, I ran it and everything seemed ok. Log file is ok.
However, I scrolled through scheduled programs and about 10 days out it started listing FBI with no info except channel POPHD (803 for me) through the NIGHT hours only for about 4 days in a row. That persisted through the end of the downloaded period. I marked them 'not to record'.
Is that a new problem?
Meanwhile, I ran it and everything seemed ok. Log file is ok.
However, I scrolled through scheduled programs and about 10 days out it started listing FBI with no info except channel POPHD (803 for me) through the NIGHT hours only for about 4 days in a row. That persisted through the end of the downloaded period. I marked them 'not to record'.
Is that a new problem?
Last edited by mafaldatv on Mon May 23, 2022 2:37 pm, edited 2 times in total.
-
- Posts: 114
- Joined: Fri Oct 02, 2015 2:52 pm
- Location:
- HTPC Specs:
I updated to latest version and while it seemed to be slow, the end result is that my icon is green and it was a success......
like the poster above, I also did mine when it was listed as a beta......
like the poster above, I also did mine when it was listed as a beta......