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

Scott & Nicole Harris snharris99 at live.com
Thu Mar 15 00:25:49 UTC 2012


> From: raymond
>> On 3/11/2012 15:45, Scott&  Nicole Harris wrote:
>>> Kill 'mythbackend', and then run 'mythjobqueue'.  Nothing more to it.
>>> You've already performed all the necessary setup for the slave backend
>>> you have doing the same task.  It will run indefinitely, processing
>>> whatever jobs you have it set up to be allowed to, until you manually
>>> terminate it through the terminal, or your distro's init system.
>> Since doing this, I had a bunch of transcodes (only, transcodes, 
>> commflags are fine) fail.  I tried them all a few times, and they always 
>> failed.
>>I only do transcode jobs on the slave backend, so today on >>a whim, I 
>>shutdown mythjobqueue and fired up mythbackend on the slave and re-tried 
>>all those failed jobs....every single one of them >>succeeded fine.

>>Transcoding requires local file access.  Commercial flagging does not.

>>Did you have the file system with the recordings mounted (as the same
>>location as on the recording host) when running mythjobqueue?

Yes, there is a /mytht)storage 1, 2, etc on both machines.  Local on the 
master backend which is not running the transcode jobs, and mounted via smb 
shares on the slave backend.

>>I'm also assuming that the recordings were recorded by some other host, 
>>right?

Also correct

>>If they were recorded by the slave backend (i.e. recording host is
>>marked as the slave backend host name), the slave backend has to be
>>running to use those recordings.

The slave backend has no tuners or storage.  I set it simply to offload 
commflag and transcode jobs to. 



More information about the mythtv-users mailing list