Page 1 of 1
Metadata Lookup errored with exit status 128
Posted: Mon Nov 02, 2015 3:30 am
by Chris
Looking through mythweb, several recent recordings are queued to Look up Metadata, when I hover over one of these, the status is "errored" with the comments saying "failed with exit status 128". Any thoughts on how to fix this are appreciated.
Re: Metadata Lookup errored with exit status 128
Posted: Mon Nov 02, 2015 4:14 pm
by bill6502
Hi,
There are 2 places in mythmetadatalookup where that exit code is used,
so looking at the mythmetadatalookup.log would be a good start.
I don't know what distribution or version of MythTV you're running but
see if the command being executed is in the log and try it yourself from
the command line. I'm GUESSING that it's a problem with the Python
grabbers and you'll see:
... Testing grabbers and metadata sites for functionality...
in the logs. And I'm also GUESSING that the command that fails
in the logs will be something like this:
/usr/share/mythtv/metadata/Television/ttvdb.py -t
That's too many guesses, but it's a start.
Re: Metadata Lookup errored with exit status 128
Posted: Sun Dec 03, 2017 9:50 am
by lindsayward
I know this post is 2 years old, but I found it when searching for this problem on my Ubuntu 14.04 MythTV 0.28 system...
I think I've solved this by:
running the last command in Bill's post, then installing missing Python packages:
Code: Select all
sudo apt-get install python-pip
sudo pip install future
sudo pip install requests-cache
or something like that.
Thanks Bill.
Unless of course I was meant to update the system as explained at:
viewtopic.php?f=30&t=2289
My metadata jobs are working again without having added a PPA or other things listed at that link.
Re: Metadata Lookup errored with exit status 128
Posted: Fri Dec 08, 2017 12:43 pm
by Gnicko
Ran in to about the same issue with Debian 8. After a software version upgrade, metadata lookup was failing with exit code 128.
It seems that, the python bindings were not part of the mythtv upgrade (or the upgraded python was part of a later batch of upgrades that didn't come along with the mythtv upgrade.)
In any case, upgrading the python packages (python-mythtv) from the Debian Multimedia depos. that come with mythtv fixed the problem.