[mythtv-users] Upgrade your system for TheTVDB update on October 1st 2017
keemllib at gmail.com
Wed Sep 20 18:02:54 UTC 2017
On 09/20/2017 12:45 PM, Jay Foster wrote:
> On 09/20/2017 08:40 AM, Jay Foster wrote:
>> On 09/20/2017 07:59 AM, Bill Meek wrote:
>>> On 09/20/2017 09:55 AM, Jay Foster wrote:
>>>> Most things seem to be working, except meta data lookups all fail with exit status 128. Any ideas?
>>> Yes, try creating: ~mythtv/.mythtv/cache/tvdb_api (writable
>>> by user mythtv of course.)
>> My backend does not have a ~mythtv/.mythtv/cache directory:
>> ls -CF /home/mythtv/.mythtv/
>> 3rdParty/ channels/ themes/
>> Cache-mythbackend-mythbox/ config.xml@ tmp/
>> Cache-mythfilldatabase-mythbox/ MythNetvision/
>> Cache-mythmetadatalookup-mythbox/ pytmdb3.cache
>> The backend does have a ~<my_user>/.mythtv/cache directory. I created the tvdb_api directory there and ran the following command from the
>> command line:
>> jay at mythbox:~$ /usr/share/mythtv/metadata/Television/ttvdb.py -l en -a US -N "77 Sunset Strip" "5"
>> /usr/local/lib/python2.7/dist-packages/urllib3/util/ssl_.py:339: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name
>> Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can
>> cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see
>> /usr/local/lib/python2.7/dist-packages/urllib3/util/ssl_.py:137: InsecurePlatformWarning: A true SSLContext object is not available. This
>> prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of
>> Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
>> jay at mythbox:~$ echo $?
>> This resulted in a ~jay/.mythtv/cache/tvdb_api/tvdb_api.sqlite file being created. Despite the warning messages, the exit status is 0.
>> I then tried running a metadata lookup from the frontend, but it still fails with exit status 128.
> I added a symlink /home/mythtv/.mythtv/cache -> /home/jay/.mythtv/cache and the metadata lookups now seem to be working.
Not sure I'd recommend sharing caches, however what are the odds that the
backend (or user mythtv) and another user will be doing metadatalookup at
the same time. Note that the user's HOME is the 1st choice for finding
.mythtv, but MYTHCONFDIR (if set) will override it.
More information about the mythtv-users