Mailing List Archive

Upgraded to 29, mythmetadata lookup failing...
I just upgraded from .27 to 29 (on Ubuntu 14.04) and most everything is now
working. I have 2 problems. One is with the new images feature and loading
pictures into the DB from the storage group doesn't seem to complete, but
I'll save that problem for another day. The bigger problem is the TV
metadata lookups are failing. In the methadatalookup.log I get:

I CoreContext metadatadownload.cpp:342 (TelevisionGrabberWorks) Television
grabber not functional. Aborting this run.


Mythbackend gives me failed with exit status 128

When I try to run ttvdb.py commandline I get responses like:
marlon:~$ /usr/share/mythtv/metadata/Television/ttvdb.py -B Sanctuary

Traceback (most recent call last):
File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 2357, in
<module>
sys.exit(main())
File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 2164, in main
seriesfound=searchseries(t, opts, series_season_ep)
File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 1217, in
searchseries
series_data = search_for_series(t, series_name, opts.language)
File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 1203, in
search_for_series
return tvdb[sid_or_name]
File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
1160, in __getitem__
sid = self._nameToSid(key)
File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
1141, in _nameToSid
selected_series = self._getSeries(name)
File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
921, in _getSeries
allSeries = self.search(series)
File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
901, in search
seriesEt = self._getetsrc(self.config['url_getSeries'] % (series))
File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
861, in _getetsrc
src = self._loadUrl(url, language=language)
File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
808, in _loadUrl
self.authorize()
File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
848, in authorize
r = self.session.post('https://api.thetvdb.com/login',
json=self.config['auth_payload'], headers=self.headers)
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 497,
in post
return self.request('POST', url, data=data, **kwargs)
File "/usr/lib/python2.7/dist-packages/requests_cache/core.py", line 128,
in request
**kwargs

Any ideas on how to fix ttvdb.py? tmdb3.py seems to work fine...
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On Thu, Sep 7, 2017 at 6:26 PM, Marlon Buchanan <mlb.linux@gmail.com> wrote:

> I just upgraded from .27 to 29 (on Ubuntu 14.04) and most everything is
> now working. I have 2 problems. One is with the new images feature and
> loading pictures into the DB from the storage group doesn't seem to
> complete, but I'll save that problem for another day. The bigger problem is
> the TV metadata lookups are failing. In the methadatalookup.log I get:
>
> I CoreContext metadatadownload.cpp:342 (TelevisionGrabberWorks)
> Television grabber not functional. Aborting this run.
>
>
> Mythbackend gives me failed with exit status 128
>
> When I try to run ttvdb.py commandline I get responses like:
> marlon:~$ /usr/share/mythtv/metadata/Television/ttvdb.py -B Sanctuary
>
> Traceback (most recent call last):
> File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 2357, in
> <module>
> sys.exit(main())
> File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 2164, in
> main
> seriesfound=searchseries(t, opts, series_season_ep)
> File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 1217, in
> searchseries
> series_data = search_for_series(t, series_name, opts.language)
> File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 1203, in
> search_for_series
> return tvdb[sid_or_name]
> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
> 1160, in __getitem__
> sid = self._nameToSid(key)
> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
> 1141, in _nameToSid
> selected_series = self._getSeries(name)
> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
> 921, in _getSeries
> allSeries = self.search(series)
> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
> 901, in search
> seriesEt = self._getetsrc(self.config['url_getSeries'] % (series))
> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
> 861, in _getetsrc
> src = self._loadUrl(url, language=language)
> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
> 808, in _loadUrl
> self.authorize()
> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
> 848, in authorize
> r = self.session.post('https://api.thetvdb.com/login',
> json=self.config['auth_payload'], headers=self.headers)
> File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 497,
> in post
> return self.request('POST', url, data=data, **kwargs)
> File "/usr/lib/python2.7/dist-packages/requests_cache/core.py", line
> 128, in request
> **kwargs
>
> Any ideas on how to fix ttvdb.py? tmdb3.py seems to work fine...
>


I apologize, I cut off one line from running ttvdb.py commandline at the
end in my cut and paste:

TypeError: request() got an unexpected keyword argument 'json'


Thanks,

Marlon
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On Thu, Sep 7, 2017 at 6:49 PM, Marlon Buchanan <mlb.linux@gmail.com> wrote:

>
>
> On Thu, Sep 7, 2017 at 6:26 PM, Marlon Buchanan <mlb.linux@gmail.com>
> wrote:
>
>> I just upgraded from .27 to 29 (on Ubuntu 14.04) and most everything is
>> now working. I have 2 problems. One is with the new images feature and
>> loading pictures into the DB from the storage group doesn't seem to
>> complete, but I'll save that problem for another day. The bigger problem is
>> the TV metadata lookups are failing. In the methadatalookup.log I get:
>>
>> I CoreContext metadatadownload.cpp:342 (TelevisionGrabberWorks)
>> Television grabber not functional. Aborting this run.
>>
>>
>> Mythbackend gives me failed with exit status 128
>>
>> When I try to run ttvdb.py commandline I get responses like:
>> marlon:~$ /usr/share/mythtv/metadata/Television/ttvdb.py -B Sanctuary
>>
>> Traceback (most recent call last):
>> File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 2357, in
>> <module>
>> sys.exit(main())
>> File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 2164, in
>> main
>> seriesfound=searchseries(t, opts, series_season_ep)
>> File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 1217, in
>> searchseries
>> series_data = search_for_series(t, series_name, opts.language)
>> File "/usr/share/mythtv/metadata/Television/ttvdb.py", line 1203, in
>> search_for_series
>> return tvdb[sid_or_name]
>> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
>> 1160, in __getitem__
>> sid = self._nameToSid(key)
>> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
>> 1141, in _nameToSid
>> selected_series = self._getSeries(name)
>> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
>> 921, in _getSeries
>> allSeries = self.search(series)
>> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
>> 901, in search
>> seriesEt = self._getetsrc(self.config['url_getSeries'] % (series))
>> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
>> 861, in _getetsrc
>> src = self._loadUrl(url, language=language)
>> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
>> 808, in _loadUrl
>> self.authorize()
>> File "/usr/lib/python2.7/dist-packages/MythTV/ttvdb/tvdb_api.py", line
>> 848, in authorize
>> r = self.session.post('https://api.thetvdb.com/login',
>> json=self.config['auth_payload'], headers=self.headers)
>> File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line
>> 497, in post
>> return self.request('POST', url, data=data, **kwargs)
>> File "/usr/lib/python2.7/dist-packages/requests_cache/core.py", line
>> 128, in request
>> **kwargs
>>
>> Any ideas on how to fix ttvdb.py? tmdb3.py seems to work fine...
>>
>
>
> I apologize, I cut off one line from running ttvdb.py commandline at the
> end in my cut and paste:
>
> TypeError: request() got an unexpected keyword argument 'json'
>
>
>

>
Okay, some progress. I used pip to install future, requests and
request_cache and now running ttvdb.py commandline works:

$ /usr/share/mythtv/metadata/Television/ttvdb.py -B Sanctuary
Banner:
http://thetvdb.com/banners/graphical/80159-g4.jpg,http://thetvdb.com/banners/graphical/80159-g5.jpg,http://thetvdb.com/banners/graphical/80159-g3.jpg,http://thetvdb.com/banners/graphical/80159-g6.jpg,http://thetvdb.com/banners/graphical/80159-g2.jpg,http://thetvdb.com/banners/graphical/80159-g.jpg,http://thetvdb.com/banners/graphical/80159-g8.jpg

But I still get the error 128 when myth does a metadata lookup for TV
shows. Any ideas?
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On 09/07/2017 11:00 PM, Marlon Buchanan wrote:
> But I still get the error 128 when myth does a metadata lookup for TV shows. Any ideas?

Maybe: sudo -H pip install --upgrade requests-cache

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On Thu, Sep 7, 2017 at 9:13 PM, Bill Meek <keemllib@gmail.com> wrote:

> On 09/07/2017 11:00 PM, Marlon Buchanan wrote:
>
>> But I still get the error 128 when myth does a metadata lookup for TV
>> shows. Any ideas?
>>
>
> Maybe: sudo -H pip install --upgrade requests-cache
>
> --
> Bill
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>


I tried that and still no luck. I ran from the commandline
mythmetadatalookup --refresh-all-artwork and it seemed to be able to use
ttvdb.py just fine. Seems very odd...
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On 09/08/2017 09:16 AM, Marlon Buchanan wrote:
>
>
> On Thu, Sep 7, 2017 at 9:13 PM, Bill Meek <keemllib@gmail.com
> <mailto:keemllib@gmail.com>> wrote:
>
> On 09/07/2017 11:00 PM, Marlon Buchanan wrote:
>
> But I still get the error 128 when myth does a metadata lookup
> for TV shows. Any ideas?
>
>
> Maybe: sudo -H pip install --upgrade requests-cache
>
> --
> Bill
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org <mailto:mythtv-users@mythtv.org>
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> <http://lists.mythtv.org/mailman/listinfo/mythtv-users>
> http://wiki.mythtv.org/Mailing_List_etiquette
> <http://wiki.mythtv.org/Mailing_List_etiquette>
> MythTV Forums: https://forum.mythtv.org
>
>
>
> I tried that and still no luck. I ran from the commandline
> mythmetadatalookup --refresh-all-artwork and it seemed to be able to
> use ttvdb.py just fine. Seems very odd...
>
>

ttvdb.py has been upgraded in 0.28 and 29 and it uses packages that do
not exist in 14.04 (trusty). See the thread at
https://lists.gt.net/mythtv/users/611123#611123 for the solution that
worked for somebody else. The real solution is to upgrade ubuntu to
16.04 or later.
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On Fri, Sep 8, 2017 at 7:04 AM, Peter Bennett <cats22@comcast.net> wrote:

>
>
> On 09/08/2017 09:16 AM, Marlon Buchanan wrote:
>
>
>
> On Thu, Sep 7, 2017 at 9:13 PM, Bill Meek <keemllib@gmail.com> wrote:
>
>> On 09/07/2017 11:00 PM, Marlon Buchanan wrote:
>>
>>> But I still get the error 128 when myth does a metadata lookup for TV
>>> shows. Any ideas?
>>>
>>
>> Maybe: sudo -H pip install --upgrade requests-cache
>>
>> --
>> Bill
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users@mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>>
>
>
> I tried that and still no luck. I ran from the commandline
> mythmetadatalookup --refresh-all-artwork and it seemed to be able to use
> ttvdb.py just fine. Seems very odd...
>
>
>
> ttvdb.py has been upgraded in 0.28 and 29 and it uses packages that do not
> exist in 14.04 (trusty). See the thread at https://lists.gt.net/mythtv/
> users/611123#611123 for the solution that worked for somebody else. The
> real solution is to upgrade ubuntu to 16.04 or later.
>
>
>
Thanks, but I've already added the appropriate packages and ttvd.py does
work commandline, so I don't think that's the problem. Mythmetadatalookup
also works commandline with ttvdb.py. So just trying to figure out why
Myth's automatic job doesn't seem to work.
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On 09/08/2017 09:10 AM, Marlon Buchanan wrote:

> Thanks, but I've already added the appropriate packages and ttvd.py does work commandline, so I don't think that's the problem.
> Mythmetadatalookup also works commandline with ttvdb.py. So just trying to figure out why Myth's automatic job doesn't seem to work.

If you don't have the actual command line from mythmetadatalookup.log already,
then try: mythbackend --setverbose system. After a recording, look in
mythmetadatalookup.log for it. The initial post here said

"Television grabber not functional."

That means that ttvdb.py was being run with the -v option just to see if
it's there (and it failed.)

Wondering if you've got more than one copy of ttvdb.py. locate -b '\ttvdb.py'
would find that.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On Fri, Sep 8, 2017 at 7:26 AM, Bill Meek <keemllib@gmail.com> wrote:

> On 09/08/2017 09:10 AM, Marlon Buchanan wrote:
>
> Thanks, but I've already added the appropriate packages and ttvd.py does
>> work commandline, so I don't think that's the problem. Mythmetadatalookup
>> also works commandline with ttvdb.py. So just trying to figure out why
>> Myth's automatic job doesn't seem to work.
>>
>
> If you don't have the actual command line from mythmetadatalookup.log
> already,
> then try: mythbackend --setverbose system. After a recording, look in
> mythmetadatalookup.log for it. The initial post here said
>
> "Television grabber not functional."
>
> That means that ttvdb.py was being run with the -v option just to see if
> it's there (and it failed.)
>
> Wondering if you've got more than one copy of ttvdb.py. locate -b
> '\ttvdb.py'
> would find that.
>
> --
> Bill
>

Hi Bill,

I previously checked for multiple ttvdb.py files, I only have one:
marlon:~$ locate -b '\ttvdb.py'
/usr/share/mythtv/metadata/Television/ttvdb.py

I set the verbosity but I didn't get much in mythmetadatalookup.log for the
a recording I just set and that ran the job. I don't see a commandline used
anywhere in the log output:

Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: C
thread_unknown mythcommandlineparser.cpp:261
9 (ConfigureLogging) mythmetadatalookup version: fixes/29
[v29.0-25-g7a40b2f] www.mythtv.org
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: C
thread_unknown mythcommandlineparser.cpp:262
1 (ConfigureLogging) Qt version: compile: 5.2.1, runtime: 5.2.1
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
thread_unknown mythcommandlineparser.cpp:262
3 (ConfigureLogging) Enabled verbose msgs: general
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
thread_unknown logging.cpp:927 (logStart) Se
tting Log Level to LOG_INFO
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
Logger logging.cpp:313 (run) Added logging t
o the console
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
thread_unknown signalhandling.cpp:194 (SetHa
ndlerPrivate) Setup Interrupt handler
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
thread_unknown signalhandling.cpp:194 (SetHa
ndlerPrivate) Setup Terminated handler
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
thread_unknown signalhandling.cpp:194 (SetHa
ndlerPrivate) Setup Segmentation fault handler
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
thread_unknown signalhandling.cpp:194 (SetHa
ndlerPrivate) Setup Aborted handler
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
thread_unknown signalhandling.cpp:194 (SetHa
ndlerPrivate) Setup Bus error handler
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
thread_unknown signalhandling.cpp:194 (SetHa
ndlerPrivate) Setup Floating point exception handler
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
thread_unknown signalhandling.cpp:194 (SetHa
ndlerPrivate) Setup Illegal instruction handler
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
thread_unknown signalhandling.cpp:194 (SetHa
ndlerPrivate) Setup Real-time signal 0 handler
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
thread_unknown signalhandling.cpp:194 (SetHa
ndlerPrivate) Setup Hangup handler
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
thread_unknown mythdirs.cpp:195 (InitializeM
ythDirs) Using runtime prefix = /usr
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
thread_unknown mythdirs.cpp:197 (InitializeM
ythDirs) Using configuration directory = /home/mythtv/.mythtv
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
CoreContext mythcorecontext.cpp:271 (Init) A
ssumed character encoding: en_US.UTF-8
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
CoreContext mythcontext.cpp:599 (LoadDatabas
eSettings) Empty LocalHostName.
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
CoreContext mythcontext.cpp:607 (LoadDatabas
eSettings) Using localhost value of firestorm
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
CoreContext mythcontext.cpp:849 (TestDBconne
ction) Start up testing connections. DB 192.168.1.109, BE , attempt 0,
status dbAwake
Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
LogForward loggingserver.cpp:302 (SyslogLogg
er) Added syslogging
Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
CoreContext mythcorecontext.cpp:1766 (InitLo
cale) Setting QT default locale to en_US
Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
CoreContext mythcorecontext.cpp:1799 (SaveLo
caleDefaults) Current locale en_US
Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
CoreContext mythlocale.cpp:123 (LoadDefaults
FromXML) Reading locale defaults from /usr/share/mythtv//locales/en_us.xml
Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
CoreContext mythtranslation.cpp:73 (load) Lo
ading en_us translation for module mythfrontend
Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
CoreContext main.cpp:112 (main) Testing grab
bers and metadata sites for functionality...
Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
SystemManager mythsystemunix.cpp:276 (run) S
tarting process manager
Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
SystemSignalManager mythsystemunix.cpp:509 (
run) Starting process signal handler
Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
SystemIOHandlerR mythsystemunix.cpp:92 (run)
Starting IO manager (read)
Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
SystemIOHandlerW mythsystemunix.cpp:92 (run)
Starting IO manager (write)
Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
CoreContext metadatadownload.cpp:342 (Televi
sionGrabberWorks) Television grabber not functional. Aborting this run.

Nothing much more in mythbackend.log either. Just the same Failed with exit
status 128... Is there a place in myth where I set the path of ttvdb.py for
mythmetadatalookup?
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On Fri, Sep 8, 2017 at 7:56 AM Marlon Buchanan <mlb.linux@gmail.com> wrote:

> On Fri, Sep 8, 2017 at 7:26 AM, Bill Meek <keemllib@gmail.com> wrote:
>
>> On 09/08/2017 09:10 AM, Marlon Buchanan wrote:
>>
>> Thanks, but I've already added the appropriate packages and ttvd.py does
>>> work commandline, so I don't think that's the problem. Mythmetadatalookup
>>> also works commandline with ttvdb.py. So just trying to figure out why
>>> Myth's automatic job doesn't seem to work.
>>>
>>
>> If you don't have the actual command line from mythmetadatalookup.log
>> already,
>> then try: mythbackend --setverbose system. After a recording, look in
>> mythmetadatalookup.log for it. The initial post here said
>>
>> "Television grabber not functional."
>>
>> That means that ttvdb.py was being run with the -v option just to see if
>> it's there (and it failed.)
>>
>> Wondering if you've got more than one copy of ttvdb.py. locate -b
>> '\ttvdb.py'
>> would find that.
>>
>> --
>> Bill
>>
>
> Hi Bill,
>
> I previously checked for multiple ttvdb.py files, I only have one:
> marlon:~$ locate -b '\ttvdb.py'
> /usr/share/mythtv/metadata/Television/ttvdb.py
>
> I set the verbosity but I didn't get much in mythmetadatalookup.log for
> the a recording I just set and that ran the job. I don't see a commandline
> used anywhere in the log output:
>
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: C
> thread_unknown mythcommandlineparser.cpp:261
> 9 (ConfigureLogging) mythmetadatalookup version: fixes/29
> [v29.0-25-g7a40b2f] www.mythtv.org
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: C
> thread_unknown mythcommandlineparser.cpp:262
> 1 (ConfigureLogging) Qt version: compile: 5.2.1, runtime: 5.2.1
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
> thread_unknown mythcommandlineparser.cpp:262
> 3 (ConfigureLogging) Enabled verbose msgs: general
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
> thread_unknown logging.cpp:927 (logStart) Se
> tting Log Level to LOG_INFO
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> Logger logging.cpp:313 (run) Added logging t
> o the console
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> thread_unknown signalhandling.cpp:194 (SetHa
> ndlerPrivate) Setup Interrupt handler
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> thread_unknown signalhandling.cpp:194 (SetHa
> ndlerPrivate) Setup Terminated handler
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> thread_unknown signalhandling.cpp:194 (SetHa
> ndlerPrivate) Setup Segmentation fault handler
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> thread_unknown signalhandling.cpp:194 (SetHa
> ndlerPrivate) Setup Aborted handler
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> thread_unknown signalhandling.cpp:194 (SetHa
> ndlerPrivate) Setup Bus error handler
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> thread_unknown signalhandling.cpp:194 (SetHa
> ndlerPrivate) Setup Floating point exception handler
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> thread_unknown signalhandling.cpp:194 (SetHa
> ndlerPrivate) Setup Illegal instruction handler
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> thread_unknown signalhandling.cpp:194 (SetHa
> ndlerPrivate) Setup Real-time signal 0 handler
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> thread_unknown signalhandling.cpp:194 (SetHa
> ndlerPrivate) Setup Hangup handler
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
> thread_unknown mythdirs.cpp:195 (InitializeM
> ythDirs) Using runtime prefix = /usr
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
> thread_unknown mythdirs.cpp:197 (InitializeM
> ythDirs) Using configuration directory = /home/mythtv/.mythtv
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> CoreContext mythcorecontext.cpp:271 (Init) A
> ssumed character encoding: en_US.UTF-8
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
> CoreContext mythcontext.cpp:599 (LoadDatabas
> eSettings) Empty LocalHostName.
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> CoreContext mythcontext.cpp:607 (LoadDatabas
> eSettings) Using localhost value of firestorm
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> CoreContext mythcontext.cpp:849 (TestDBconne
> ction) Start up testing connections. DB 192.168.1.109, BE , attempt 0,
> status dbAwake
> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> LogForward loggingserver.cpp:302 (SyslogLogg
> er) Added syslogging
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
> CoreContext mythcorecontext.cpp:1766 (InitLo
> cale) Setting QT default locale to en_US
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> CoreContext mythcorecontext.cpp:1799 (SaveLo
> caleDefaults) Current locale en_US
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: N
> CoreContext mythlocale.cpp:123 (LoadDefaults
> FromXML) Reading locale defaults from /usr/share/mythtv//locales/en_us.xml
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> CoreContext mythtranslation.cpp:73 (load) Lo
> ading en_us translation for module mythfrontend
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> CoreContext main.cpp:112 (main) Testing grab
> bers and metadata sites for functionality...
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> SystemManager mythsystemunix.cpp:276 (run) S
> tarting process manager
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> SystemSignalManager mythsystemunix.cpp:509 (
> run) Starting process signal handler
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> SystemIOHandlerR mythsystemunix.cpp:92 (run)
> Starting IO manager (read)
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> SystemIOHandlerW mythsystemunix.cpp:92 (run)
> Starting IO manager (write)
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I
> CoreContext metadatadownload.cpp:342 (Televi
> sionGrabberWorks) Television grabber not functional. Aborting this run.
>
> Nothing much more in mythbackend.log either. Just the same Failed with
> exit status 128... Is there a place in myth where I set the path of
> ttvdb.py for mythmetadatalookup?
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


What's the output of 'dpkg -l | grep myth'
--
-Thomas
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On Fri, Sep 8, 2017 at 11:55 AM, Thomas Mashos <thomas@mashos.com> wrote:

>
>
> On Fri, Sep 8, 2017 at 7:56 AM Marlon Buchanan <mlb.linux@gmail.com>
> wrote:
>
>> On Fri, Sep 8, 2017 at 7:26 AM, Bill Meek <keemllib@gmail.com> wrote:
>>
>>> On 09/08/2017 09:10 AM, Marlon Buchanan wrote:
>>>
>>> Thanks, but I've already added the appropriate packages and ttvd.py does
>>>> work commandline, so I don't think that's the problem. Mythmetadatalookup
>>>> also works commandline with ttvdb.py. So just trying to figure out why
>>>> Myth's automatic job doesn't seem to work.
>>>>
>>>
>>> If you don't have the actual command line from mythmetadatalookup.log
>>> already,
>>> then try: mythbackend --setverbose system. After a recording, look in
>>> mythmetadatalookup.log for it. The initial post here said
>>>
>>> "Television grabber not functional."
>>>
>>> That means that ttvdb.py was being run with the -v option just to see if
>>> it's there (and it failed.)
>>>
>>> Wondering if you've got more than one copy of ttvdb.py. locate -b
>>> '\ttvdb.py'
>>> would find that.
>>>
>>> --
>>> Bill
>>>
>>
>> Hi Bill,
>>
>> I previously checked for multiple ttvdb.py files, I only have one:
>> marlon:~$ locate -b '\ttvdb.py'
>> /usr/share/mythtv/metadata/Television/ttvdb.py
>>
>> I set the verbosity but I didn't get much in mythmetadatalookup.log for
>> the a recording I just set and that ran the job. I don't see a commandline
>> used anywhere in the log output:
>>
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> C thread_unknown mythcommandlineparser.cpp:261
>> 9 (ConfigureLogging) mythmetadatalookup version: fixes/29
>> [v29.0-25-g7a40b2f] www.mythtv.org
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> C thread_unknown mythcommandlineparser.cpp:262
>> 1 (ConfigureLogging) Qt version: compile: 5.2.1, runtime: 5.2.1
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> N thread_unknown mythcommandlineparser.cpp:262
>> 3 (ConfigureLogging) Enabled verbose msgs: general
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> N thread_unknown logging.cpp:927 (logStart) Se
>> tting Log Level to LOG_INFO
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I Logger logging.cpp:313 (run) Added logging t
>> o the console
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I thread_unknown signalhandling.cpp:194 (SetHa
>> ndlerPrivate) Setup Interrupt handler
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I thread_unknown signalhandling.cpp:194 (SetHa
>> ndlerPrivate) Setup Terminated handler
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I thread_unknown signalhandling.cpp:194 (SetHa
>> ndlerPrivate) Setup Segmentation fault handler
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I thread_unknown signalhandling.cpp:194 (SetHa
>> ndlerPrivate) Setup Aborted handler
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I thread_unknown signalhandling.cpp:194 (SetHa
>> ndlerPrivate) Setup Bus error handler
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I thread_unknown signalhandling.cpp:194 (SetHa
>> ndlerPrivate) Setup Floating point exception handler
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I thread_unknown signalhandling.cpp:194 (SetHa
>> ndlerPrivate) Setup Illegal instruction handler
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I thread_unknown signalhandling.cpp:194 (SetHa
>> ndlerPrivate) Setup Real-time signal 0 handler
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I thread_unknown signalhandling.cpp:194 (SetHa
>> ndlerPrivate) Setup Hangup handler
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> N thread_unknown mythdirs.cpp:195 (InitializeM
>> ythDirs) Using runtime prefix = /usr
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> N thread_unknown mythdirs.cpp:197 (InitializeM
>> ythDirs) Using configuration directory = /home/mythtv/.mythtv
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I CoreContext mythcorecontext.cpp:271 (Init) A
>> ssumed character encoding: en_US.UTF-8
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> N CoreContext mythcontext.cpp:599 (LoadDatabas
>> eSettings) Empty LocalHostName.
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I CoreContext mythcontext.cpp:607 (LoadDatabas
>> eSettings) Using localhost value of firestorm
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I CoreContext mythcontext.cpp:849 (TestDBconne
>> ction) Start up testing connections. DB 192.168.1.109, BE , attempt 0,
>> status dbAwake
>> Sep 8 07:42:33 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I LogForward loggingserver.cpp:302 (SyslogLogg
>> er) Added syslogging
>> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> N CoreContext mythcorecontext.cpp:1766 (InitLo
>> cale) Setting QT default locale to en_US
>> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I CoreContext mythcorecontext.cpp:1799 (SaveLo
>> caleDefaults) Current locale en_US
>> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> N CoreContext mythlocale.cpp:123 (LoadDefaults
>> FromXML) Reading locale defaults from /usr/share/mythtv//locales/en_
>> us.xml
>> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I CoreContext mythtranslation.cpp:73 (load) Lo
>> ading en_us translation for module mythfrontend
>> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I CoreContext main.cpp:112 (main) Testing grab
>> bers and metadata sites for functionality...
>> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I SystemManager mythsystemunix.cpp:276 (run) S
>> tarting process manager
>> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I SystemSignalManager mythsystemunix.cpp:509 (
>> run) Starting process signal handler
>> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I SystemIOHandlerR mythsystemunix.cpp:92 (run)
>> Starting IO manager (read)
>> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I SystemIOHandlerW mythsystemunix.cpp:92 (run)
>> Starting IO manager (write)
>> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]:
>> I CoreContext metadatadownload.cpp:342 (Televi
>> sionGrabberWorks) Television grabber not functional. Aborting this run.
>>
>> Nothing much more in mythbackend.log either. Just the same Failed with
>> exit status 128... Is there a place in myth where I set the path of
>> ttvdb.py for mythmetadatalookup?
>>
>>
>> _______________________________________________
>>
> What's the output of 'dpkg -l | grep myth'
> --
> -Thomas
>
>
The output on the particular backend I'm troubleshooting right now is:

ii libmyth
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 amd64 Common
library code for MythTV and add-on modules (runtime)
rc libmyth-29-0
2:0.29.0~master.20160509.0bfcd20-0ubuntu0mythbuntu3 amd64 Common
library code for MythTV and add-on modules (runtime)
ii libmyth-python
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 all Python
library to access some MythTV features
ii libmythes-1.2-0
2:1.2.2-1ubuntu2 amd64 simple
thesaurus library
ii libmythtv-perl
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 all Perl
library to access some MythTV features
rc mythbuntu-bare-client 2.6.3
all Mythbuntu Bare Client
ii mythbuntu-common 0.74
all Mythbuntu application
support functions
ii mythbuntu-control-centre 0.64.1
all Mythbuntu
Configuration Application
ii mythes-en-au 2.1-5.4
all Australian English
Thesaurus for OpenOffice.org
ii mythes-en-us
1:4.2.1-0ubuntu1.1 all English
Thesaurus for LibreOffice
ii mythgallery
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 amd64 Image
gallery/slideshow add-on module for MythTV
ii mythtv-backend
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 amd64 Personal
video recorder application (server)
ii mythtv-common
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 amd64 Personal
video recorder application (common data)
rc mythtv-database
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 all Personal
video recorder application (database)
ii mythtv-dbg
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 amd64 Debug
symbols for mythtv packages
ii mythtv-frontend
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 amd64 Personal
video recorder application (client)
ii mythtv-status 0.10.4-1
all Show the status of a
MythTV backend
ii mythtv-transcode-utils
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 amd64 Utilities
used for transcoding MythTV tasks
ii mythweb
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 all Web
interface add-on module for MythTV
ii mythzoneminder
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 amd64 view
status and display footage recorded with zoneminder
ii php-mythtv
2:29.0+fixes.20170903.7a40b2f-0ubuntu0mythbuntu4 all PHP
Bindings for MythTV
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On 09/08/2017 09:55 AM, Marlon Buchanan wrote:
...
> Sep 8 07:42:34 firestorm mythmetadatalookup: mythmetadatalookup[19256]: I CoreContext metadatadownload.cpp:342 (Televi
> sionGrabberWorks) Television grabber not functional. Aborting this run.


> Nothing much more in mythbackend.log either. Just the same Failed with exit status 128... Is there a place in myth where I set the path of
> ttvdb.py for mythmetadatalookup?


mythbackend --setverbose --system will cause the backend and any programs
it calls to run with -v system. But if you want to run mythmetadatalookup
from the command line, then just add: -v system. That will show the actual
command being executed.

Haven't found the answer to your question though.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On 9/8/2017 10:10 AM, Marlon Buchanan wrote:
>
>
> On Fri, Sep 8, 2017 at 7:04 AM, Peter Bennett <cats22@comcast.net
> <mailto:cats22@comcast.net>> wrote:
>
>
>
> On 09/08/2017 09:16 AM, Marlon Buchanan wrote:
>>
>>
>> On Thu, Sep 7, 2017 at 9:13 PM, Bill Meek <keemllib@gmail.com
>> <mailto:keemllib@gmail.com>> wrote:
>>
>> On 09/07/2017 11:00 PM, Marlon Buchanan wrote:
>>
>> But I still get the error 128 when myth does a metadata
>> lookup for TV shows. Any ideas?
>>
>>
>> Maybe: sudo -H pip install --upgrade requests-cache
>>
>> --
>> Bill
>>
>> I tried that and still no luck. I ran from the commandline
>> mythmetadatalookup --refresh-all-artwork and it seemed to be able
>> to use ttvdb.py just fine. Seems very odd...
>>
>>
>
> ttvdb.py has been upgraded in 0.28 and 29 and it uses packages that
> do not exist in 14.04 (trusty). See the thread at
> https://lists.gt.net/mythtv/users/611123#611123
> <https://lists.gt.net/mythtv/users/611123#611123> for the solution
> that worked for somebody else. The real solution is to upgrade
> ubuntu to 16.04 or later.
>
>
>
> Thanks, but I've already added the appropriate packages and ttvd.py does
> work commandline, so I don't think that's the problem.
> Mythmetadatalookup also works commandline with ttvdb.py. So just trying
> to figure out why Myth's automatic job doesn't seem to work.
>

When you run from the command line, are you running as the same user
that runs mythbackend? If not, try running as the mythbackend user. That
will show if you installed the python packages as root so all users can
use them.

HTH,
Helen
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
>>
>
> Thanks, but I've already added the appropriate packages and ttvd.py does
> work commandline, so I don't think that's the problem. Mythmetadatalookup
> also works commandline with ttvdb.py. So just trying to figure out why
> Myth's automatic job doesn't seem to work.
>
>
When you run from the command line, are you running as the same user that
runs mythbackend? If not, try running as the mythbackend user. That will
show if you installed the python packages as root so all users can use them.

HTH,
Helen

______________________________


I installed the packages as root and they run run fine from command line
as the same user as mythbackend.
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
Nothing much more in mythbackend.log either. Just the same Failed with exit
> status 128... Is there a place in myth where I set the path of ttvdb.py for
> mythmetadatalookup?
>


mythbackend --setverbose --system will cause the backend and any programs
it calls to run with -v system. But if you want to run mythmetadatalookup
from the command line, then just add: -v system. That will show the actual
command being executed.

Haven't found the answer to your question though.



In my pre upgrade mythmetadatalookup logs (before upgrade from .27 to 29)
I see the command called ttvdb.py command called successfully shortly after
the "Testing grabbers and metadata sites for functionality..." message. See
below:

Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: C
thread_unknown mythcommandlineparser.cpp:2595 (ConfigureLogging)
mythmetadatalookup version: fixes/0.27 [v0.27.5-4-ge2a11c9] www.mythtv.org
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: C
thread_unknown mythcommandlineparser.cpp:2597 (ConfigureLogging) Qt
version: compile: 4.8.1, runtime: 4.8.6
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: N
thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging) Enabled
verbose msgs: general
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: N
thread_unknown logging.cpp:907 (logStart) Setting Log Level to LOG_INFO
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
Logger logging.cpp:308 (run) Added logging to the console
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Interrupt
handler
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Terminated
handler
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup
Segmentation fault handler
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Aborted
handler
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus error
handler
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Floating
point exception handler
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Illegal
instruction handler
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Real-time
signal 0 handler
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: N
thread_unknown mythdirs.cpp:55 (InitializeMythDirs) Using runtime prefix =
/usr
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: N
thread_unknown mythdirs.cpp:68 (InitializeMythDirs) Using configuration
directory = /home/mythtv/.mythtv
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
CoreContext mythcorecontext.cpp:257 (Init) Assumed character encoding:
en_US.UTF-8
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: N
CoreContext mythcontext.cpp:504 (LoadDatabaseSettings) Empty LocalHostName.
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
CoreContext mythcontext.cpp:512 (LoadDatabaseSettings) Using localhost
value of firestorm
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
CoreContext mythcontext.cpp:693 (TestDBconnection) Testing network
connectivity to '192.168.1.109'
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
SystemManager mythsystemunix.cpp:275 (run) Starting process manager
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
SystemSignalManager mythsystemunix.cpp:510 (run) Starting process signal
handler
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
SystemIOHandlerW mythsystemunix.cpp:91 (run) Starting IO manager (write)
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
SystemIOHandlerR mythsystemunix.cpp:91 (run) Starting IO manager (read)
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
LogForward loggingserver.cpp:1373 (forwardMessage) New Client: (#1)
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
LogForward loggingserver.cpp:295 (SyslogLogger) Added syslogging
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: N
CoreContext mythcorecontext.cpp:1634 (InitLocale) Setting QT default locale
to en_US
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
CoreContext mythcorecontext.cpp:1667 (SaveLocaleDefaults) Current locale
en_US
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: N
CoreContext mythlocale.cpp:121 (LoadDefaultsFromXML) Reading locale
defaults from /usr/share/mythtv//locales/en_us.xml
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
CoreContext mythtranslation.cpp:65 (load) Loading en_us translation for
module mythfrontend
Sep 6 18:59:39 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
CoreContext main.cpp:128 (main) Testing grabbers and metadata sites for
functionality...
Sep 6 18:59:40 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
CoreContext main.cpp:135 (main) All grabbers tested and working.
Continuing...
Sep 6 18:59:40 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
CoreContext mythcorecontext.cpp:426 (ConnectCommandSocket) MythCoreContext:
Connecting to backend server: 192.168.1.109:6543 (try 1 of 1)
Sep 6 18:59:40 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
CoreContext mythcorecontext.cpp:1547 (CheckProtoVersion) Using protocol
version 77
Sep 6 18:59:40 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
MetadataDownload metadatagrabber.cpp:455 (RunGrabber) Running Grabber:
/usr/share/mythtv/metadata/Television/ttvdb.py -l en -a US -N Snowfall The
Rubicon
Sep 6 18:59:40 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
MetadataDownload metadatacommon.cpp:1188 (ParseMetadataItem) Result Found,
Season 1 Episode 10
Sep 6 18:59:41 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
MetadataDownload metadatagrabber.cpp:455 (RunGrabber) Running Grabber:
/usr/share/mythtv/metadata/Television/ttvdb.py -l en -a US -N 328092 The
Rubicon
Sep 6 18:59:41 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
MetadataDownload metadatacommon.cpp:1188 (ParseMetadataItem) Result Found,
Season 1 Episode 10
Sep 6 18:59:41 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
MetadataDownload metadatadownload.cpp:176 (run) Returning Metadata Results:
Snowfall 1 10
Sep 6 18:59:44 firestorm mythmetadatalookup: mythmetadatalookup[22515]: N
CoreContext main.cpp:183 (main) MythMetadataLookup run complete.
Sep 6 18:59:44 firestorm mythmetadatalookup: mythmetadatalookup[22515]: I
CoreContext mythcontext.cpp:1194 (~MythContext) Waiting for threads to exit.
Sep 6 19:59:30 firestorm mythmetadatalookup: mythmetadatalookup[5538]: C
thread_unknown mythcommandlineparser.cpp:2595 (ConfigureLogging)
mythmetadatalookup version: fixes/0.27 [v0.27.5-4-ge2a11c9] www.mythtv.org


Now in the logs I don't get any mention of the ttvdb.py call by
mythmetadatalookup... Does mytmetadatalookup fail before it gets there???

Sep 7 10:19:12 firestorm mythmetadatalookup: mythmetadatalookup[8395]: I
CoreContext mythcontext.cpp:1194 (~MythContext) Waiting for threads to exit.
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: C
thread_unknown mythcommandlineparser.cpp:2619 (ConfigureLogging)
mythmetadatalookup version: fixes/29 [v29.0-25-g7a40b2f] www.mythtv.org
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: C
thread_unknown mythcommandlineparser.cpp:2621 (ConfigureLogging) Qt
version: compile: 5.2.1, runtime: 5.2.1
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: N
thread_unknown mythcommandlineparser.cpp:2623 (ConfigureLogging) Enabled
verbose msgs: general
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: N
thread_unknown logging.cpp:927 (logStart) Setting Log Level to LOG_INFO
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
Logger logging.cpp:313 (run) Added logging to the console
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Interrupt
handler
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Terminated
handler
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup
Segmentation fault handler
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Aborted
handler
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus error
handler
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Floating
point exception handler
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Illegal
instruction handler
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Real-time
signal 0 handler
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Hangup
handler
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: N
thread_unknown mythdirs.cpp:195 (InitializeMythDirs) Using runtime prefix =
/usr
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: N
thread_unknown mythdirs.cpp:197 (InitializeMythDirs) Using configuration
directory = /home/mythtv/.mythtv
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
CoreContext mythcorecontext.cpp:271 (Init) Assumed character encoding:
en_US.UTF-8
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: N
CoreContext mythcontext.cpp:599 (LoadDatabaseSettings) Empty LocalHostName.
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
CoreContext mythcontext.cpp:607 (LoadDatabaseSettings) Using localhost
value of firestorm
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
CoreContext mythcontext.cpp:849 (TestDBconnection) Start up testing
connections. DB 192.168.1.109, BE , attempt 0, status dbAwake
Sep 7 14:29:35 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
LogForward loggingserver.cpp:302 (SyslogLogger) Added syslogging
Sep 7 14:29:36 firestorm mythmetadatalookup: mythmetadatalookup[14349]: N
CoreContext mythcorecontext.cpp:1766 (InitLocale) Setting QT default locale
to en_US
Sep 7 14:29:36 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
CoreContext mythcorecontext.cpp:1799 (SaveLocaleDefaults) Current locale
en_US
Sep 7 14:29:36 firestorm mythmetadatalookup: mythmetadatalookup[14349]: N
CoreContext mythlocale.cpp:123 (LoadDefaultsFromXML) Reading locale
defaults from /usr/share/mythtv//locales/en_us.xml
Sep 7 14:29:36 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
CoreContext mythtranslation.cpp:73 (load) Loading en_us translation for
module mythfrontend
Sep 7 14:29:36 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
CoreContext main.cpp:112 (main) Testing grabbers and metadata sites for
functionality...
Sep 7 14:29:36 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
SystemManager mythsystemunix.cpp:276 (run) Starting process manager
Sep 7 14:29:36 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
SystemSignalManager mythsystemunix.cpp:509 (run) Starting process signal
handler
Sep 7 14:29:36 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
SystemIOHandlerW mythsystemunix.cpp:92 (run) Starting IO manager (write)
Sep 7 14:29:36 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
SystemIOHandlerR mythsystemunix.cpp:92 (run) Starting IO manager (read)
Sep 7 14:29:36 firestorm mythmetadatalookup: mythmetadatalookup[14349]: I
CoreContext metadatadownload.cpp:342 (TelevisionGrabberWorks) Television
grabber not functional. Aborting this run.
Sep 7 16:37:56 firestorm mythmetadatalookup: mythmetadatalookup[29098]: C
thread_unknown mythcommandlineparser.cpp:2619 (ConfigureLogging)
mythmetadatalookup version: fixes/29 [v29.0-25-g7a40b2f] www.mythtv.org

I'm sure the logging and call tracing is different two versions later, but
it naybe the problem is myth's call to mythmetadatalookup or ttvdb.py
failing or it's using the wrong path for mythmetadatalookup or ttvdb.py? As
I mentioned before, mythmetadatalookup works fine via commandline, and it
does show proper calls and results from ttvdb.py. The frontend works
properly as well when initiating a metadata lookup in the videos (not
recordings) from the frontend using ttvdb.py.


I've tried running the tools as root, my user and tge mythtv user from cli
and they work. I'm just struggling to figure out what is going wrong...
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
<snip>
>
> I'm sure the logging and call tracing is different two versions later, but
> it naybe the problem is myth's call to mythmetadatalookup or ttvdb.py
> failing or it's using the wrong path for mythmetadatalookup or ttvdb.py? As
> I mentioned before, mythmetadatalookup works fine via commandline, and it
> does show proper calls and results from ttvdb.py. The frontend works
> properly as well when initiating a metadata lookup in the videos (not
> recordings) from the frontend using ttvdb.py.
>
>
> I've tried running the tools as root, my user and tge mythtv user from cli
> and they work. I'm just struggling to figure out what is going wrong...
>
>
> Well, I've run out of ideas. Short of tracing through the code I can't
come up with any ideas on why this isn't working. For now, I've just
disabled the metadata lookup jobs in mythtv for each recording rule,
deleted the failed jobs in mysql, and now I just run mythmetadata via a
cron job daily. Not ideal, but seems to work. Weird that the job fails...
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On 09/09/2017 07:14 AM, Marlon Buchanan wrote:
>
> I'm sure the logging and call tracing is different two versions later, but it naybe the problem is myth's call to mythmetadatalookup or
> ttvdb.py failing or it's using the wrong path for mythmetadatalookup or ttvdb.py? As I mentioned before, mythmetadatalookup works fine via
> commandline, and it does show proper calls and results from ttvdb.py. The frontend works properly as well when initiating a metadata lookup in
> the videos (not recordings) from the frontend using ttvdb.py.
>
My typo a few posts back. To watch the calls to mythmetadatalookup
in the backend log, use: mythbackend --setverbose system (not --system
as I typed earlier.) Then look in the backend and mythmetadatalookup
logs to see what's being executed. Either run the lookup job yourself
from the frontend or let the backend run one after a recording.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On Wed, Sep 13, 2017 at 4:45 PM, Bill Meek <keemllib@gmail.com> wrote:

> On 09/09/2017 07:14 AM, Marlon Buchanan wrote:
>
>>
>> I'm sure the logging and call tracing is different two versions later,
>> but it naybe the problem is myth's call to mythmetadatalookup or ttvdb.py
>> failing or it's using the wrong path for mythmetadatalookup or ttvdb.py? As
>> I mentioned before, mythmetadatalookup works fine via commandline, and it
>> does show proper calls and results from ttvdb.py. The frontend works
>> properly as well when initiating a metadata lookup in the videos (not
>> recordings) from the frontend using ttvdb.py.
>>
>> My typo a few posts back. To watch the calls to mythmetadatalookup
> in the backend log, use: mythbackend --setverbose system (not --system
> as I typed earlier.) Then look in the backend and mythmetadatalookup
> logs to see what's being executed. Either run the lookup job yourself
> from the frontend or let the backend run one after a recording.
>
> --
> Bill
> _______________________________________________
>
>
Hi Bill.

I noticed that typo and set the verbosity correctly and the logs I posted
where the result of that which had no more info in the logs about
mythmetadata's call to ttvdb in either log when a job was executed. Just
the same "Television grabber not functional" message in
mythmetadatalookup.log and "Metadata Lookup Errored..." message in
mythbackend.log. This is basically what I get everytime a metadata job is
run, with verbosity set higher.

mythmetadatalookup.log:

Sep 13 16:57:49 firestorm mythmetadatalookup: mythmetadatalookup[7403]: I
CoreContext main.cpp:112 (main) Testing grabbers and metadata sites for
functionality...
Sep 13 16:57:49 firestorm mythmetadatalookup: mythmetadatalookup[7403]: I
SystemManager mythsystemunix.cpp:276 (run) Starting process manager
Sep 13 16:57:49 firestorm mythmetadatalookup: mythmetadatalookup[7403]: I
SystemIOHandlerR mythsystemunix.cpp:92 (run) Starting IO manager (read)
Sep 13 16:57:49 firestorm mythmetadatalookup: mythmetadatalookup[7403]: I
SystemSignalManager mythsystemunix.cpp:509 (run) Starting process signal
handler
Sep 13 16:57:49 firestorm mythmetadatalookup: mythmetadatalookup[7403]: I
SystemIOHandlerW mythsystemunix.cpp:92 (run) Starting IO manager (write)
Sep 13 16:57:50 firestorm mythmetadatalookup: mythmetadatalookup[7403]: I
CoreContext metadatadownload.cpp:342 (TelevisionGrabberWorks) Television
grabber not functional. Aborting this run.

mythbackend.log:

Sep 13 16:57:48 firestorm mythbackend: mythbackend[2751]: I Metadata_21956
jobqueue.cpp:2157 (DoMetadataLookupThread) JobQueue: Metadata Lookup
Starting for "The Orville":"Old Wounds" recorded from channel 8113 at
2017-09-11T01:00:00Z
Sep 13 16:57:48 firestorm mythbackend: mythbackend[2751]: I CoreContext
mythdbcon.cpp:435 (PurgeIdleConnections) New DB connection, total: 6
Sep 13 16:57:50 firestorm mythbackend: mythbackend[2751]: E Metadata_21956
jobqueue.cpp:2221 (DoMetadataLookupThread) JobQueue: Metadata Lookup
Errored: "The Orville":"Old Wounds" recorded from channel 8113 at
2017-09-11T01:00:00Z (Failed with exit status 128)

Maybe the setverbose isn't working properly, but I get the " Sent
'SET_VERBOSE system' message" when I run the command. I've also tried
changing the loglevel.

When I use --verbose commandline with mythmetadatalookup I can see the
calls and everything happens correctly. I can't figure out what myth is
doing mythmetadata lookup This combined with the lack of information in the
log is why I'm stumped. I used to get more detail from mythmetadata.log in
the .27, even without turning up verbosity. Seems like something is logged
differently or something is failing before it ever even gets to call
ttvdb.py
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
> On 09/08/2017 09:10 AM, Marlon Buchanan wrote:
>
> > Thanks, but I've already added the appropriate packages and ttvd.py does
work commandline, so I don't think that's the problem.
> > Mythmetadatalookup also works commandline with ttvdb.py. So just trying
to figure out why Myth's automatic job doesn't seem to work.
>
> If you don't have the actual command line from mythmetadatalookup.log
> already, then try: mythbackend --setverbose system. After a recording,
look
> in mythmetadatalookup.log for it. The initial post here said
>
> "Television grabber not functional."
>
> That means that ttvdb.py was being run with the -v option just to see if
it's
> there (and it failed.)
>
What is the output of the following commands (if your distro has ttvdb.py
and tmdb3.py in a different location you may need to search for them and
correct the path as appropriate). Make sure to run as the same user in same
environment as is running the backend.

/usr/local/share/mythtv/metadata/Television/ttvdb.py -v
/usr/local/share/mythtv/metadata/Movie/tmdb3.py -v
/usr/local/share/mythtv/metadata/Movie/tmdb3.py -t

I was getting the same error. In my case on a clean install (but heavily
customised inside a docker container) I found that I was missing group
execute permissions on ttvdb.py and tmdb3.py. I also had no ~/.mythtv/cache
directory and ttvdb.py failed until I manually created the cache directory
with appropriate permissions. I also used pip to install requests_cache "pip
install requests-cache".

$/usr/local/share/mythtv/metadata/Television/ttvdb.py -v
Traceback (most recent call last):
File "/usr/local/share/mythtv/metadata/Television/ttvdb.py", line 1074, in
<module>
os.mkdir(cache_dir)
OSError: [Errno 2] No such file or directory:
'/home/mythtv/.mythtv/cache/tvdb_api/'

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On Fri, Sep 15, 2017 at 9:50 PM, Mark Perkins <perkins1724@hotmail.com>
wrote:

> > On 09/08/2017 09:10 AM, Marlon Buchanan wrote:
> >
> > > Thanks, but I've already added the appropriate packages and ttvd.py
> does
> work commandline, so I don't think that's the problem.
> > > Mythmetadatalookup also works commandline with ttvdb.py. So just trying
> to figure out why Myth's automatic job doesn't seem to work.
> >
> > If you don't have the actual command line from mythmetadatalookup.log
> > already, then try: mythbackend --setverbose system. After a recording,
> look
> > in mythmetadatalookup.log for it. The initial post here said
> >
> > "Television grabber not functional."
> >
> > That means that ttvdb.py was being run with the -v option just to see if
> it's
> > there (and it failed.)
> >
> What is the output of the following commands (if your distro has ttvdb.py
> and tmdb3.py in a different location you may need to search for them and
> correct the path as appropriate). Make sure to run as the same user in same
> environment as is running the backend.
>
> /usr/local/share/mythtv/metadata/Television/ttvdb.py -v
> /usr/local/share/mythtv/metadata/Movie/tmdb3.py -v
> /usr/local/share/mythtv/metadata/Movie/tmdb3.py -t
>
> I was getting the same error. In my case on a clean install (but heavily
> customised inside a docker container) I found that I was missing group
> execute permissions on ttvdb.py and tmdb3.py. I also had no ~/.mythtv/cache
> directory and ttvdb.py failed until I manually created the cache directory
> with appropriate permissions. I also used pip to install requests_cache
> "pip
> install requests-cache".
>
> $/usr/local/share/mythtv/metadata/Television/ttvdb.py -v
> Traceback (most recent call last):
> File "/usr/local/share/mythtv/metadata/Television/ttvdb.py", line 1074,
> in
> <module>
> os.mkdir(cache_dir)
> OSError: [Errno 2] No such file or directory:
> '/home/mythtv/.mythtv/cache/tvdb_api/'
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>

I have 0.28 (0.28.1+fixes.20170903) installed on Ubuntu 16.04.3 and also
cannot get some metadata lookup tasks to work. Movie lookups using tmdb.py
work but television show lookups using ttvdb.py have been failing for about
a week.

Running:
/usr/share/mythtv/metadata/Television/ttvdb.py -t
returns:
No handlers could be found for logger "MythTV.ttvdb.tvdb_exceptions"

I have previously installed requests_cache and a few other missing modules
using pip. Can anyone here suggest anything else I can try to fix this,
short of reinstalling from scratch?

Thanks,
William
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
>
> What is the output of the following commands (if your distro has ttvdb.py
> and tmdb3.py in a different location you may need to search for them and
> correct the path as appropriate). Make sure to run as the same user in same
> environment as is running the backend.
>
> /usr/local/share/mythtv/metadata/Television/ttvdb.py -v
> /usr/local/share/mythtv/metadata/Movie/tmdb3.py -v
> /usr/local/share/mythtv/metadata/Movie/tmdb3.py -t
>
> I was getting the same error. In my case on a clean install (but heavily
> customised inside a docker container) I found that I was missing group
> execute permissions on ttvdb.py and tmdb3.py. I also had no ~/.mythtv/cache
> directory and ttvdb.py failed until I manually created the cache directory
> with appropriate permissions. I also used pip to install requests_cache
> "pip
> install requests-cache".
>
> $/usr/local/share/mythtv/metadata/Television/ttvdb.py -v
> Traceback (most recent call last):
> File "/usr/local/share/mythtv/metadata/Television/ttvdb.py", line 1074,
> in
> <module>
> os.mkdir(cache_dir)
> OSError: [Errno 2] No such file or directory:
> '/home/mythtv/.mythtv/cache/tvdb_api/'
>
> I have a .mythtv/cache file with proper permissions. All apropriate python
modules are installed. ttvdb.py, tmdb3.py and mythmetadatalookup all work
fine commandline using the same user as runs them as mythbackend. The only
place that fails to run them is withing mythtbackend mythmetadatalookup
jobs. I now run mythmetadatalookup in a cron job and that works fine, but
is not ideal.

08:05:06 marlon:~$ sudo -u mythtv
/usr/share/mythtv/metadata/Movie/tmdb3.py -v
<?xml version='1.0' encoding='UTF-8'?>
<grabber>
<name>TheMovieDB.org V3</name>
<author>Raymond Wagner</author>
<thumbnail>tmdb.png</thumbnail>
<command>tmdb3.py</command>
<type>movie</type>
<description>Search and metadata downloads for themoviedb.org
</description>
<version>0.3.7</version>
<accepts>tmdb.py</accepts>
<accepts>tmdb.pl</accepts>
</grabber>
08:05:10 marlon:~$ sudo -u mythtv /usr/share/mythtv/metadata/Movie/tmdb3.py
-t
Everything appears in order.
08:05:13 marlon:~$ sudo -u mythtv
/usr/share/mythtv/metadata/Television/ttvdb.py -v
<grabber>
<name>TheTVDB.com</name>
<author>R.D.Vaughan</author>
<thumbnail>ttvdb.png</thumbnail>
<command>ttvdb.py</command>
<type>television</type>
<description>Search and metadata downloads for thetvdb.com</description>
<version>2.0.0</version>
</grabber>


>
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
Ok, Fedora 26 has the following versions and it's failing so I'm assuming
at least one of these is not new enough...

# rpm -q python2-future python2-requests python-requests-cache
python2-future-0.16.0-4.fc26.noarch
python2-requests-2.13.0-1.fc26.noarch
python-requests-cache-0.4.6-8.fc26.noarch

Thanks,
Richard
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On Sun, 2017-09-17 at 07:45 -0500, Richard Shaw wrote:
> Ok, Fedora 26 has the following versions and it's failing so I'm
> assuming at least one of these is not new enough...
>
> # rpm -q python2-future python2-requests python-requests-cache
> python2-future-0.16.0-4.fc26.noarch
> python2-requests-2.13.0-1.fc26.noarch
> python-requests-cache-0.4.6-8.fc26.noarch
>
> Thanks,
> Richard


The python-requests-cache package needs to be 0.4.7 or better to
support the json argument on one of the functions. I emailed the
package owner on 8/31 to ask for an update, but there's been no
response.

David

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On 09/17/2017 08:45 AM, Richard Shaw wrote:
> Ok, Fedora 26 has the following versions and it's failing so I'm
> assuming at least one of these is not new enough...
>
> # rpm -q python2-future python2-requests python-requests-cache
> python2-future-0.16.0-4.fc26.noarch
> python2-requests-2.13.0-1.fc26.noarch
> python-requests-cache-0.4.6-8.fc26.noarch
>
> Thanks,
> Richard
>
>
Those are all newer than what I have, apart from requests-cache. I have
0.4.10 for that.
You might want to check python-urllib3 also, I have version 1.13.1

If the fedora packages do not have sufficiently up to date versions you
can update them with pip.
Re: Upgraded to 29, mythmetadata lookup failing... [ In reply to ]
On 09/16/2017 10:11 AM, Marlon Buchanan wrote:
>>
>> What is the output of the following commands (if your distro has ttvdb.py
>> and tmdb3.py in a different location you may need to search for them and
>> correct the path as appropriate). Make sure to run as the same user in same
>> environment as is running the backend.
>>
>> /usr/local/share/mythtv/metadata/Television/ttvdb.py -v
>> /usr/local/share/mythtv/metadata/Movie/tmdb3.py -v
>> /usr/local/share/mythtv/metadata/Movie/tmdb3.py -t
>>
>> I was getting the same error. In my case on a clean install (but heavily
>> customised inside a docker container) I found that I was missing group
>> execute permissions on ttvdb.py and tmdb3.py. I also had no ~/.mythtv/cache
>> directory and ttvdb.py failed until I manually created the cache directory
>> with appropriate permissions. I also used pip to install requests_cache
>> "pip
>> install requests-cache".
>>
>> $/usr/local/share/mythtv/metadata/Television/ttvdb.py -v
>> Traceback (most recent call last):
>> File "/usr/local/share/mythtv/metadata/Television/ttvdb.py", line 1074,
>> in
>> <module>
>> os.mkdir(cache_dir)
>> OSError: [Errno 2] No such file or directory:
>> '/home/mythtv/.mythtv/cache/tvdb_api/'
>>
>> I have a .mythtv/cache file with proper permissions. All apropriate python
> modules are installed. ttvdb.py, tmdb3.py and mythmetadatalookup all work
> fine commandline using the same user as runs them as mythbackend. The only
> place that fails to run them is withing mythtbackend mythmetadatalookup
> jobs. I now run mythmetadatalookup in a cron job and that works fine, but
> is not ideal.
>
> 08:05:06 marlon:~$ sudo -u mythtv
> /usr/share/mythtv/metadata/Movie/tmdb3.py -v
> <?xml version='1.0' encoding='UTF-8'?>
> <grabber>
> <name>TheMovieDB.org V3</name>
> <author>Raymond Wagner</author>
> <thumbnail>tmdb.png</thumbnail>
> <command>tmdb3.py</command>
> <type>movie</type>
> <description>Search and metadata downloads for themoviedb.org
> </description>
> <version>0.3.7</version>
> <accepts>tmdb.py</accepts>
> <accepts>tmdb.pl</accepts>
> </grabber>
> 08:05:10 marlon:~$ sudo -u mythtv /usr/share/mythtv/metadata/Movie/tmdb3.py
> -t
> Everything appears in order.
> 08:05:13 marlon:~$ sudo -u mythtv
> /usr/share/mythtv/metadata/Television/ttvdb.py -v
> <grabber>
> <name>TheTVDB.com</name>
> <author>R.D.Vaughan</author>
> <thumbnail>ttvdb.png</thumbnail>
> <command>ttvdb.py</command>
> <type>television</type>
> <description>Search and metadata downloads for thetvdb.com</description>
> <version>2.0.0</version>
> </grabber>

I'm stumped. I'd try running the tests in two steps,
like this (to simulate the mythtv environment better):

sudo --set-home --login --user=mythtv
/usr/local/share/mythtv/metadata/Television/ttvdb.py -v

Thinking that user mythtv has a copy of some module
in it's directory (done with pip install run without
sudo for example.)

OK, three steps: echo $PYTHONPATH while you're user mythtv.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

1 2  View All