Difference between revisions of "Schedules Direct URL Change"
(maybe the 3rd & final address?) |
(Rewrite lede a bit for clarity) |
||
| Line 1: | Line 1: | ||
| − | + | As some have heard, on November 1st, 2014, the existing SD service is changing. This article is intended to be a short discussion of options for MythTV users. | |
| − | As some have heard, on November 1st, 2014, the existing SD | ||
| − | service is changing. This | ||
| − | options for MythTV users. | ||
Ideally, there would be a DNS change and the IP address for the existing (hard coded) hostname | Ideally, there would be a DNS change and the IP address for the existing (hard coded) hostname | ||
| − | would be pointed to a new IP address and no action would be | + | would be pointed to a new IP address and no action would be required by MythTV SD users. However, the owner of that hostname (which |
| − | required by MythTV SD users. However, the owner of that hostname (which | + | is not SD) could 'retire' that DNS record at any time leaving MythTV SD users out of service. |
| − | is not SD) could 'retire' that DNS record at any time leaving MythTV SD users | + | |
| − | out of service. | + | Because of this, users of older versions of MythTV will need to make one of two changes in order to continue retrieving SD data: |
| + | |||
| + | 1) Modify your MythTV sources to use a different DNS name for the Schedules Direct data source, or, if you can't easily do that, | ||
| + | |||
| + | 2) Add a line to your hosts file, which overrides the IP address returned by DNS for the name | ||
| + | "baked" into the copy of MythTV you're running. | ||
| + | |||
== What '''must''' users do prior to November 1st, 2014? == | == What '''must''' users do prior to November 1st, 2014? == | ||
| Line 14: | Line 17: | ||
0.27 and 0.28-pre users should keep their systems | 0.27 and 0.28-pre users should keep their systems | ||
up to date with current fixes. The fix for this | up to date with current fixes. The fix for this | ||
| − | issue hasn't been released as of the last update of | + | issue hasn't been released as of the last update of this Wiki. When released, information about it will be added here. |
| − | this Wiki. When released, information about it will be added here. | ||
{| border="1" cellspacing="0" cellpadding="5" style="float: center;border-collapse:collapse; border-color:#8eabd0; background:#e7edf5" | {| border="1" cellspacing="0" cellpadding="5" style="float: center;border-collapse:collapse; border-color:#8eabd0; background:#e7edf5" | ||
| Line 34: | Line 36: | ||
|} | |} | ||
<br> | <br> | ||
| + | |||
== What '''must''' be done on November 1st. == | == What '''must''' be done on November 1st. == | ||
| Line 42: | Line 45: | ||
== Is there anything users can do to try the replacement now? == | == Is there anything users can do to try the replacement now? == | ||
| − | Yes, perhaps the simplest is to make the following entry in | + | Yes, perhaps the simplest is to make the following entry in the backend's /etc/hosts file: |
| − | the backend's /etc/hosts file: | ||
<pre> | <pre> | ||
| Line 49: | Line 51: | ||
</pre> | </pre> | ||
| − | The new server is working well. But the more users testing it, | + | The new server is working well. But the more users testing it, the better. (It would be nice to discover any problems now rather than on 11/1.) |
| − | the better. (It would be nice to discover any problems now rather than on 11/1.) | ||
Is the /etc/hosts entry a proper solution? No, because IP addresses can change. | Is the /etc/hosts entry a proper solution? No, because IP addresses can change. | ||
| Line 67: | Line 68: | ||
The mythtv-users mailing list under the thread: ''Schedules Direct DataDirect replacement service testing''. | The mythtv-users mailing list under the thread: ''Schedules Direct DataDirect replacement service testing''. | ||
Or, it's [http://www.gossamer-threads.com/lists/mythtv/users/576759 archive]). | Or, it's [http://www.gossamer-threads.com/lists/mythtv/users/576759 archive]). | ||
| − | Please don't start new testing threads. | + | Please don't start new testing threads. If you make a report on the testing thread, please mention which version of MythTV you're running (if you run mythfilldatabase by hand, it will tell you, right at the beginning of its logs). |
Discussions on the developer's [http://irc.mythtv.org/ircLog/channel/4/2014-10-08 channel]. | Discussions on the developer's [http://irc.mythtv.org/ircLog/channel/4/2014-10-08 channel]. | ||
| Line 91: | Line 92: | ||
<br> | <br> | ||
| − | == Can users that build from source make a change now? == | + | == Can users that build from source make a change now? ==1 |
Yes, locate the line to change with the following command and | Yes, locate the line to change with the following command and | ||
replace the hostname with the new one above. Be prepared to | replace the hostname with the new one above. Be prepared to | ||
Revision as of 20:13, 12 October 2014
As some have heard, on November 1st, 2014, the existing SD service is changing. This article is intended to be a short discussion of options for MythTV users.
Ideally, there would be a DNS change and the IP address for the existing (hard coded) hostname would be pointed to a new IP address and no action would be required by MythTV SD users. However, the owner of that hostname (which is not SD) could 'retire' that DNS record at any time leaving MythTV SD users out of service.
Because of this, users of older versions of MythTV will need to make one of two changes in order to continue retrieving SD data:
1) Modify your MythTV sources to use a different DNS name for the Schedules Direct data source, or, if you can't easily do that,
2) Add a line to your hosts file, which overrides the IP address returned by DNS for the name "baked" into the copy of MythTV you're running.
Contents
What must users do prior to November 1st, 2014?
0.27 and 0.28-pre users should keep their systems up to date with current fixes. The fix for this issue hasn't been released as of the last update of this Wiki. When released, information about it will be added here.
| Version | Commit | Release Date |
|---|---|---|
| 0.27 | TBA | TBA |
| 0.28-pre | TBA | TBA |
What must be done on November 1st.
If the above was followed, nothing.
Users running 0.26 and below should use the solution in the following section.
Is there anything users can do to try the replacement now?
Yes, perhaps the simplest is to make the following entry in the backend's /etc/hosts file:
54.85.117.227 webservices.schedulesdirect.tmsdatadirect.com
The new server is working well. But the more users testing it, the better. (It would be nice to discover any problems now rather than on 11/1.)
Is the /etc/hosts entry a proper solution? No, because IP addresses can change. It's not a bad solution, but it's certainly not as good as running on 35.0.
Note: The IP address has already changed twice from the original one posted here.
Are there any other sources of information about the change?
Yes.
The announcement from SD.
List of open issues, also from SD.
The mythtv-users mailing list under the thread: Schedules Direct DataDirect replacement service testing. Or, it's archive). Please don't start new testing threads. If you make a report on the testing thread, please mention which version of MythTV you're running (if you run mythfilldatabase by hand, it will tell you, right at the beginning of its logs).
Discussions on the developer's channel.
Cast of characters (both of them.)
| Abbreviated Name | URL | Description |
|---|---|---|
| TMS-DD | docs.tms.tribune.com webservices.schedulesdirect.tmsdatadirect.com | Tribune hosted Datadirect Server (going away) |
| SD-DD | dd.schedulesdirect.org | SD hosted DataDirect Server |
== Can users that build from source make a change now? ==1 Yes, locate the line to change with the following command and replace the hostname with the new one above. Be prepared to remove the change when the official commit is pushed.
git grep webservices.schedulesdirect.tmsdatadirect.com
