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

[Scott & Nicole Harris]

>>> 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).
>> I was wondering (it amazes me the things that run through my head when 
>> I'm
>> supposed to be sleeping) if it might be something with permissions.
>> However, as far as I can tell, all the mythtv_storage* folders have the 
>> same
>> permissions, which were set with the -R flag...
>>
>> drwxrwsr-x   4 mythtv mythtv     0 2012-03-17 08:03 mythtv_storage1
>> drwxrwsr-x   3 mythtv mythtv     0 2012-03-17 08:03 mythtv_storage2
>> drwxrwsr-x   3 mythtv mythtv     0 2012-03-17 08:03 mythtv_storage3
>> drwxrwsr-x   3 mythtv mythtv     0 2012-03-17 08:03 mythtv_storage4
>> drwxrwsr-x   3 mythtv mythtv     0 2012-03-17 08:03 mythtv_storage5
>>
>> I went through each of the recordings folder in those directories and all
>> recordings have mythtv:mythtv as ownership and all new recordings seem to
>> have the same permissions of -rwxr--r--
>>
>> So if it's a permissions thing, I would have to assume that
>> mythjobqueue/transcode is running not as the mythtv user but my local 
>> user
>> that I launched mythjobqueue with, whereas mythbackend is starting using 
>> the
>> mythtv user (as expected).  The only thing that's throwing me off is some
>> transcodes are working (though they're far fewer than those that fail), 
>> and
>> as far as I can tell there is no permission difference on any new 
>> recordings
>> between mythtv_storage*/recordings folders.
>>
>> While testing all this, I am not u sing any scripts or anything to start
>> mythjobqueue, I'm just starting it from terminal....
>>
>> mythjobqueue --logfile /tmp/mythjobqueue.log&

>Yeah, that means it's running as your user, who doesn't have permission
>to write to the recordings directories.

>Try with the start script that Michael W posted.

>Mike

I have upgraded to 0.25.  I've put Michael W's (thanks Michael W!) script in 
place, but removed the --logfile part because 0.25 doesn't like it.  Don't 
have any recordings scheduled until tomorrow, so I'll keep you posted.