[mythtv-users] Metadata Lookup Errored in Backend Log - On Every Recording.

[Greg Grotsky]

On Mon, Oct 27, 2014 at 12:08 PM, Bill Meek <keemllib at gmail.com> wrote:

> Hi,
>
> I'm stumped. Here's 4 suggestions (in reverse order of what I'd do, but
> quickest.)
> After each, re-try the metadata download:
>
>    Boot mythbox (which I hate because if it works the problem is masked.)
>
>    Restart the mythbackend (bad for the same reason.)
>
>    delete the cache in: ~mythtv/.mythtv/cache/mythmetadatalookup-mythbox/
> data*/?/*
>    (still would hide the problem.)
>
>    Apply this patch and make another run, look at the output in
> /tmp/easy.log
>    http://pastebin.com/kjQ4LKVW . The question being, why can't the
> backend
>    find the Python bindings yet when you run tmdb3.py from the command line
>    it works OK.


Hi Bill, new information! I have been using an init script to start the
backend in /etc/init.d/mythbackend. I have found that when I run
mythbackend manually from a command prompt instead of running the init
script it works! I found the command that is used to start mythbackend and
tried to execute it to start the server:

start-stop-daemon --start --quiet --pidfile /var/run/mythtv/mythbackend.pid
--user spikeygg --chuid spikeygg --exec /mythtv/local64/bin/mythbackend --
--daemon --logpath /var/log/mythtv --pidfile /var/run/mythtv/mythbackend.pid

When I ran mythfrontend while logged in as spikeygg and tried to lookup it
also worked! So where does that leave me? When root runs that command it
breaks my bindings? Any ideas on how to correct it?

To confirm this I did a "sudo su" became root, issued the same command
above to start the backend (start-stop-daemon), ran the frontend to kick
off the metadatalookup and it failed as usual. :-/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20141027/aa6f3e04/attachment.html>