[mythtv-users] 0.25 lookup metadata as part of jobqueue?
Michael T. Dean
mtdean at thirdcontact.com
Sat Mar 17 16:30:22 UTC 2012
On 03/17/2012 09:40 AM, Michael Watson wrote:
> On 17/03/2012 11:46 PM, Scott& Nicole Harris wrote:
>>>> OK, I've attached the logs of two transcodes I just tried that both
>>>> failed. I then ran killed mythjobqueue and started mythbackend on the
>>>> slave and re-queued the jobs and both went through fine.
>>>> 2012-03-16 21:34:58.739 Generating Keyframe Index
>>>> 2012-03-16 21:34:58.755 Opening
>>>> 2012-03-16 21:34:58.768 Couldn't open input file, error #-22
>>>> 2012-03-16 21:34:58.783 Transcoding
>>>> /mythtv_storage5/recordings/1081_20120315220000.mpg failed
>>>> 2012-03-16 21:34:58.789 Transcode: delete old file: waiting while
>>>> program is in use.
>>>> 2012-03-16 21:34:58.798 Transcode: program is no longer in use.
>>>> 2012-03-16 21:34:58.814 Deleting
>>>> 2012-03-16 21:34:58.824 Requesting delete for file
>>>> 2012-03-16 21:38:14.437 Opening
>>>> 2012-03-16 21:38:14.447 Couldn't open input file, error #-22
>>>> 2012-03-16 21:38:14.458 Transcoding
>>>> /mythtv_storage2/recordings/1131_20120315220200.mpg failed
>>>> 2012-03-16 21:38:14.463 Transcode: delete old file: waiting while
>>>> program is in use.
>>>> 2012-03-16 21:38:14.471 Transcode: program is no longer in use.
>>>> 2012-03-16 21:38:14.481 Deleting
>>>> 2012-03-16 21:38:14.489 Requesting delete for file
>>> In both cases, mythtranscode was unable to create the temporary file in
>>> which it planned to transcode.
>>> It looks like you're running mythjobqueue as a user that doesn't have
>>> permissions on (at least some of) the /mythtv_storage*/recordings/
>>> directories (meaning that mythtranscode then inherits the
>>> user/permissions of mythjobqueue). This may also explain why some of
>>> the transcodes succeed--because some of those directories have more lax
>>> permissions. You should check ownership of all your recordings to
>>> ensure they're correct (likely mythtv user) so that you don't have
>>> problems deleting them at some later date.
>>> FWIW, I don't think the --user argument works for mythjobqueue, so you'd
>>> need some other way to start it as the right user. I'm clueless on
>>> upstart, so I'll let someone else help you figure out how that's done.
>>> And, BTW, thanks for helping figure this out. Once it's figured out,
>>> perhaps we can get Ubuntu to start shipping a proper mythjobqueue start
>>> script (or at least get one on the wiki).
> At one point I was starting mythjobqueue via a init.d script (from
> memory I think I modified the Fedora script found on the wiki)
> I dont recall why I stopped using it, but I found it better (or easier)
> to run the full backend with a Dummy Tuner configured. (As it
> wasnt/isn't an "approved" configuration for a backend without any tuners
Perhaps because in 0.24, mythjobqueue doesn't allow your master backend
to shut down automatically. It does in 0.25.
More information about the mythtv-users