<div>try launching mythbackend with the verbose logging enabled. </div>
<div> </div>
<div>mythbackend --help<br>Valid options are:<br>-l or --logfile filename Writes STDERR and STDOUT messages to filename<br>-p or --pidfile filename Write PID of mythbackend to filename<br>-d or --daemon Runs mythbackend as a daemon
<br>-v or --verbose debug-level Prints more information<br> Accepts any combination (separated by comma)<br> of all,none,quiet,record,playback,channel,<br> osd,file,schedule,network,commflag,audio,
<br> libav,jobqueue<br>--printexpire List of auto-expire programs<br>--printsched Upcoming scheduled programs<br>--testsched Test run scheduler (ignore existing schedule)
<br>--resched Force the scheduler to update<br>--nosched Do not perform any scheduling<br>--version Version information<br><br>-- <br>Thanks,<br>Devan Lippman
<a href="mailto:devan@lippman.net">devan@lippman.net</a> <br> </div>
<div> </div>
<div><span class="gmail_quote">On 6/7/05, <b class="gmail_sendername">Egeekial</b> <<a href="mailto:egeekial@comcast.net">egeekial@comcast.net</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Well, I decided to take a look at recordedmarkup, and the last entry<br>that's in there is marked 6-4-2005. I've recorded at least something
<br>every day. So for some reason, things are getting put into the<br>recordedmarkup table. Any idea where I should start looking in order to<br>debug?<br><br>Garry Cook wrote:<br><br>>On 6/7/05, <a href="mailto:kanetse@gmail.com">
kanetse@gmail.com</a> <<a href="mailto:kane.tse@gmail.com">kane.tse@gmail.com</a>> wrote:<br>><br>><br>>>Sometimes the recordedmarkup table needs to be repaired in the database:<br>>><br>>>>>From a command prompt, run
<br>>><br>>>mysql -u mythtv mythconverg -p<br>>><br>>>And then within mysql:<br>>><br>>>REPAIR TABLE recordedmarkup;<br>>><br>>>That should fix the table, if that was your problem. However, you
<br>>>will have to get MythTV to re-flag the commericals on the shows which<br>>>were flagged while the table was corrupted.<br>>><br>>><br>><br>>Hey, thanx! That worked perfectly for me. All of my old recordings
<br>>have their commercial flagging back, and as you stated, recordings<br>>since the table broke need to be reflagged. After reflagging, they<br>>work perfectly, perhaps even better than before the upgrade to 18.1
<br>>(from 18).<br>><br>>I'm wondering if turning the 'commercial flagging immediately' (or<br>>whatever it's called) option back on will break it again. Don't have<br>>time to check it right now, but perhaps tonight I can give it a shot.
<br>><br>>Who works on the commercial flagging code (Chris Peterson???)? Is<br>>there anyone that might want some log info or something to help track<br>>the problem down if I find that it does re-occur? Let me know...
<br>><br>>--Garry<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">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>><br>><br>><br>><br><br><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">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div>