[mythtv-users] 0.25 lookup metadata as part of jobqueue?

Michael T. Dean mtdean at thirdcontact.com
Fri Mar 16 23:29:42 UTC 2012


On 03/16/2012 07:15 AM, Scott & Nicole Harris wrote:
>>>> Ah, OK.  Using --logfile is correct with 0.24.  However, 0.24 doesn't
>>>> pass logging options through to child processes.  I don't know of any
>>>> way to get 0.24 to actually tell mythtranscode to log messages when it's
>>>> called from the backend.  When you change the script (make a copy of the
>>>> original before editing it) to start mythjobqueue, instead, and to use
>>>> --logfile /var/log/mythtv/mythjobqueue.log do you get mythjobqueue
>>>> logs?  I'm guessing they--like mythbackend logs--wouldn't show much more
>>>> than start/stop, but since the transcode is failing under mythjobqueue,
>>>> seeing the failure might give us enough information to find out why
>>>> mythtranscode is failing.  If not, you may need to try just running
>>>> mythtranscode to see if it fails, and why.
>>> OK, just to make sure I understand.  I can start mythjobqueue
>>> with --logfile
>>> /var/log/mythtv/mythjobqueue.log.  That should give me logging for what
>>> mythjobqueue is doing?  I have a bunch of recordings going tonight that
>>> I'll
>>> be transcoding so if that's correct, I'll shutdown mythbackend and fire
>>> up
>>> mythjobqueue and see what I get for you guys.
>> Exactly.  Thanks.
> Thanks, I only asked because there's no mention of the --logfile fag in the
> wiki entry for mythjobqueue.  Anyways, I tried it last night and 3 of 5
> transcodes failed.  However, mythtranscode.log and mythjobqueue.log are both
> completely blank, even with using the -- logfile flag.

That's likely permissions problems or something.  Try logging somewhere 
that anyone could write a file--such as /tmp/mythtranscode.log

Mike


More information about the mythtv-users mailing list