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

[Scott & Nicole Harris]

>>> Date: Sun, 11 Mar 2012 16:15:25 -0400
>>> From: raymond at wagnerrp.com
>>> To: mythtv-users at mythtv.org
>>> Subject: Re: [mythtv-users] 0.25 lookup metadata as part of jobqueue?
>>> 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.

>Could you post some logs?  There should be no difference between the two, 
>as the 'mythjobqueue'
>application really doesn't do anything.  It's nothing more than a wrapper 
>around
>an isolated thread in one of the shared libraries.

I'd be happy to, but I don't seem to have any.  mythbackend.log only has 
info in it for the jobs run today via mythbackend; nothing for the jobs run 
with mythbackend killed and only mythjobqueue running.  However, what's 
really odd is mythtranscode.log has nothing in it at all post Feb 18.