<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<br><br><div><div id="SkyDrivePlaceholder"></div><br>> On 03/14/2012 08:23 PM, Scott & Nicole Harris wrote:<br>> >>>> Date: Sun, 11 Mar 2012 16:15:25 -0400<br>> >>>> From: raymond@wagnerrp.com<br>> >>>> To: mythtv-users@mythtv.org<br>> >>>> Subject: Re: [mythtv-users] 0.25 lookup metadata as part of jobqueue?<br>> >>>> Kill 'mythbackend', and then run 'mythjobqueue'. Nothing more to it.<br>> >>>> You've already performed all the necessary setup for the slave backend<br>> >>>> you have doing the same task. It will run indefinitely, processing<br>> >>>> whatever jobs you have it set up to be allowed to, until you manually<br>> >>>> terminate it through the terminal, or your distro's init system.<br>> >>> Since doing this, I had a bunch of transcodes (only, transcodes, commflags<br>> >>> are fine) fail.<br>> >>> I tried them all a few times, and they always failed. I only do transcode<br>> >>> jobs on the slave backend,<br>> >>> so today on a>>whim, I shutdown mythjobqueue and fired up mythbackend on<br>> >>> the slave and<br>> >>> re-tried all those failed jobs....every single one of them succeeded<br>> >>> fine.<br>> >> Could you post some logs? There should be no difference between the two,<br>> >> as the 'mythjobqueue'<br>> >> application really doesn't do anything. It's nothing more than a wrapper<br>> >> around<br>> >> an isolated thread in one of the shared libraries.<br>> > I'd be happy to, but I don't seem to have any. mythbackend.log only has<br>> > info in it for the jobs run today via mythbackend; nothing for the jobs run<br>> > with mythbackend killed and only mythjobqueue running. However, what's<br>> > really odd is mythtranscode.log has nothing in it at all post Feb 18.<br>> <br>> How is mythbackend started by your distro?<br>> <br>> It should use (assuming 0.25beta):<br>> <br>> mythbackend --logpath /path/to/dir<br>> <br>> and note that it must be a directory. It can't use --logfile <br>> /path/to/file or -l /path/to/dir/or/file or --logpath /path/to/file or <br>> logging won't work (and, with current master, --logfile or -l will give <br>> you a nice error telling you to fix it). Or, if you want to use syslog, <br>> you can, as described at:<br>> <br>> http://www.mythtv.org/wiki/Category:Syslog_Configuration_Files<br>> http://www.mythtv.org/wiki/Rsyslog_Configuration<br>> (and if your distro uses a different implementation of syslog--not <br>> rsyslog--please feel free to create and add a configuration file for <br>> your flavor of syslog).<br>> <br>> Mike<br></div><div><br></div><div>Mythbackend logs are fine (I get plenty of data when mythbackend is actually running). I wouldn't expect to have anything in mythbackend.log for the failed stuff that I tried using just mythjobqueue because the point of the exercise was to try having my jobs done without having mythbackend running. Now, why mythtranscode.log is blank is a bit perplexing to me.</div> </div></body>
</html>