[mythtv-users] OS X MythFillDatabase hangs using 100% CPU

[Ian Clark]

On 16 September 2011 11:33, Eric Holt <ericsh at wvcom.net> wrote:
> Hi all.  I just moved my backend from some 4 year old hardware to a refurb'd Mac Mini Server.
>
> All is working great, except for the scheduled MythFillDatabase runs. They are hanging, eating up 100% cpu usage on one of the cores.
>
> Looking through the logs, I found this relevant piece of information:
>
>        sh: wget: command not found
>
> Oddly enough, I installed wget in a directory in the user's path (/usr/local/bin/wget).  The user can run wget without specifying the path.
>
> The myth user can also run mythfilldatabase from Console without any problem.  If I run it manually, it runs perfectly fine, no issues.
>
Are these two users the same?

It sounds like the myth user can't see wget, or can't see wget when
the backend is started (which spawns filldatabase), this probably
means PATH isn't setup correctly at the point when mythbackend is
started.

How are you changing to the myth user, it's quite easy to do and
accidentally pull in the environment of the user you're changing from.

How do you start mythbackend?

You could wrap it in a scrip that does:

echo "Current myth path:" > /some/log/file.log
echo $PATH >> /some/log/file.log
mythbackend

or even

echo "Current myth env:" > /some/log/file.log
set >> /some/log/file.log
mythbackend