<div class="gmail_quote">On Sun, Aug 21, 2011 at 2:12 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 08/20/2011 09:03 AM, Christopher Kerr wrote:<br>
> I've got a weird problem that'll make me sound mad, and (thanks to an<br>
> unrelated problem) I don't even have logs to back it up.<br>
><br>
> Tonight (and on two other occasions in the last week or so) I've had a<br>
> recording start, appear in the recordings list, and later disappear<br>
> again. When I check the Previously Recorded screen, it insists that<br>
> the show wasn't recording because a previous showing had been.<br>
><br>
> Since every occasion thus far has been on a first screening (new<br>
> episodes of Top Gear, Midsomer Murders and Marchlands) the duplicate<br>
> detection is clearly misfiring - indeed, since the recordings<br>
> start successfully, I can only presume that the recordings are being<br>
> detected as duplicates of themselves!<br>
><br>
> On an unrelated but important note: is there any way to check where a<br>
> running instance of mythbackend is logging? On Ubuntu, the logs should<br>
> be in /var/logs/mythtv/mythbackend.log , but my most recent logs are<br>
> from the 24th of July...<br>
><br>
<br>
</div></div>Sounds like garbage EIT data messing with start/end times during the<br>
recording? (Though some other stuff would have to happen to actually<br>
make the recording disappear, too.)<br></blockquote><div><br></div><div>Definitely not, EIT is disabled for every channel.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Would definitely need logs to diagnose. Only your mythbackend start<br>
script/configuration could tell you where it's logging--or someone else<br>
who uses your distro and its start script/configuration. Note, also,<br>
that if the user running mythbackend doesn't have permissions on the<br>
/var/logs/mythtv directory or the /var/logs/mythtv/mythbackend.log file,<br>
it won't actually log to that file...<br></blockquote><div><br></div><div>Checked the script, it's definitely supposed to be logging to /var/log/mythtv/mythbackend.log. It also definitely isn't.</div><div><br>
</div><div>I tried starting mythbackend from the command line with the --logfile switch - should I expect to see errors in the console if there are file permission problems?</div><div><br></div><div>- Chris</div></div>