<br><br><div class="gmail_quote">On Mon, Feb 15, 2010 at 6:13 PM, Nick Morrott <span dir="ltr"><<a href="mailto:knowledgejunkie@gmail.com">knowledgejunkie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 15 February 2010 22:32, Josh White <<a href="mailto:jaw1959@gmail.com">jaw1959@gmail.com</a>> wrote:<br>
> For some reason, my backend stopped making new recordings. According to the<br>
> upcoming recordings page, I have no upcoming recordings (though I have about<br>
> 55 shows set to record at any time, on any channel). The olympics are not<br>
> recording, though I've set them to record. This is a new problem for me,<br>
> and I'd appreciate any help finding my way to a solution. I don't know what<br>
> logs, what output, what whatever I should be checking in this case. The<br>
> database seems to work to some degree, as all the recordings I made prior to<br>
> 8:30pm on 2/13/10 are available with all their metadata.<br>
<br>
</div>This behaviour could indicate an issue with the database, an issue<br>
with your input connections configuration, or an issue with your<br>
listings. Do you see listings in the programme guide?<br>
<br>
You can use the <a href="http://optimize_mythdb.pl" target="_blank">optimize_mythdb.pl</a> script (included with MythTV) to<br>
diagnose and correct problems with your database. It may well be<br>
possible for a crashed table to stop the scheduler from running<br>
properly. The script should fix any such tables.<br>
<br>
Check your capture card and input connections configuration in<br>
mythtv-setup. You shouldn't need to touch your video sources if you're<br>
successfully receiving listings, but if you have capture hardware that<br>
can change device node on reboot you might want to check that the<br>
defined capture card(s) in the system are correct.<br>
<br>
The mythbackend logfile is the one to check for problems with<br>
scheduling and recording. You can add more verbose logging details if<br>
you need to whilst debugging (see mythbackend -v help). You can also<br>
run:<br>
<br>
$ mythbackend --printsched<br>
<br>
to print the output of the scheduler's last run.<br>
<br>
If you do notice any errors in the backend log, post them (trim the<br>
log if possible) here.<br>
<br>
Cheers,<br>
Nick<br>
<br>
--<br>
Nick Morrott<br>
<br>
MythTV Official wiki: <a href="http://mythtv.org/wiki/" target="_blank">http://mythtv.org/wiki/</a><br>
MythTV users list archive: <a href="http://www.gossamer-threads.com/lists/mythtv/users" target="_blank">http://www.gossamer-threads.com/lists/mythtv/users</a><br>
<br>
"An investment in knowledge always pays the best interest." - Benjamin Franklin<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</blockquote></div><br><br>Fixed (I believe). I ran the <a href="http://optimize_mythdb.pl">optimize_mythdb.pl</a> script, then a mythfilldatabase, and now it's working. I thought I had a weekly cron job running the optimize script, but it seems I should investigate to see if it's working.<br>
<br>Thanks for the assistance!<br>