<div class="gmail_quote">On Mon, Mar 23, 2009 at 8:03 PM, Paulin <span dir="ltr"><<a href="mailto:paulin@spextreme.com">paulin@spextreme.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello all,<div><br></div><div>I've had a myth system setup for a while now. I'm using Trunk 19992. It's been running very well and in fact over this weekend was the first time I had to reboot it in 14 days.</div>
<div><br>Anyway tonight my wife went to start watching something and it was responding very slowly. So I logged in and checked it out. </div><div><br></div><div>On the frontend she was in the screen to select a show to watch. Top command showed the backend pegging the CPU at 100%. Frontend wouldn't respond. I looked in the frontend log file and saw it spitting out the Frame Sync Error as below</div>
<div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px">2009-03-23 19:42:59.801 [ac3 @ 0xb7040770]frame sync error<br></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><br></div></blockquote><div><br></div><div>This continued. The log right before the frame sync is</div><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px">
2009-03-23 19:42:59.592 AFD: Opened codec 0x9fc6ba0, id(MPEG2VIDEO) type(Video)<br>2009-03-23 19:42:59.592 AFD: codec AC3 has 6 channels<br>2009-03-23 19:42:59.593 AFD: Opened codec 0x9fc7290, id(AC3) type(Audio)<br>2009-03-23 19:42:59.698 [mpeg2video @ 0xb7040770]skipped MB in I frame at 22 0<br>
2009-03-23 19:42:59.698 [mpeg2video @ 0xb7040770]skipped MB in I frame at 5 6<br>2009-03-23 19:42:59.698 [mpeg2video @ 0xb7040770]skipped MB in I frame at 27 13<br>2009-03-23 19:42:59.698 [mpeg2video @ 0xb7040770]invalid mb type in I Frame at 22 15<br>
2009-03-23 19:42:59.698 [mpeg2video @ 0xb7040770]skipped MB in I frame at 42 16<br>2009-03-23 19:42:59.698 [mpeg2video @ 0xb7040770]skipped MB in I frame at 3 23<br>2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]skipped MB in I frame at 16 30<br>
2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]skipped MB in I frame at 4 39<br>2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]invalid mb type in I Frame at 40 39<br>2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]skipped MB in I frame at 5 40<br>
2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]skipped MB in I frame at 41 40<br>2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]skipped MB in I frame at 1 41<br>2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]ac-tex damaged at 42 41<br>
2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]invalid mb type in I Frame at 2 42<br>2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]invalid mb type in I Frame at 40 42<br>2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]invalid mb type in I Frame at 40 43<br>
2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]skipped MB in I frame at 1 44<br>2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]skipped MB in I frame at 41 44<br>2009-03-23 19:42:59.699 [mpeg2video @ 0xb7040770]Warning MVs not available<br>
2009-03-23 19:42:59.793 [mpeg2video @ 0xb7040770]ac-tex damaged at 4 8<br>2009-03-23 19:42:59.793 [mpeg2video @ 0xb7040770]slice mismatch<br>2009-03-23 19:42:59.796 [mpeg2video @ 0xb7040770]Warning MVs not available<br>2009-03-23 19:42:59.801 [ac3 @ 0xb7040770]frame sync error<br>
</blockquote><div><div><br></div></div><div>Any ideas what happened. Like I said its been working fine for over a month. No updates or anything were done other then a reboot 3 days ago. Could this be a corrupted video file or bad hard disk? Machine is only 6 months old.</div>
<div><br></div><div>Thoughts. How can I fix this or where should I look?</div><div><br></div><div>Thanks</div><div>steve</div><div></div></blockquote><div><br></div><div>Well I seem to have fixed the problem but not sure why it happened. The problem was happening when going to the watch recording screen and myth web when the MythBackend attempted to generate a preview for one of the recordings. The error started popping up in the frontend log but a ps showed a bunch of mythbackend --generate-preview processes. I deleted the offending mpg file (using rm -f xxx.mpg) then reloading. Now everything appears to be working fine.</div>
<div><br></div><div>Anyone have any thoughts as to what the problem could have been? Why would the recording cause such a problem. Also should there be any checks in mythbackend to protect from this type of error?</div>
<div><br></div><div>steve</div></div>