<div dir="ltr"><div class="gmail_quote">On Sat, Aug 16, 2008 at 4:38 AM, Allen Edwards <span dir="ltr"><<a href="mailto:allen.edwards@oldpaloalto.com">allen.edwards@oldpaloalto.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I don't know what to title this. Yesterday, my frontend started<br>locking up when I tried to watch a show. I restart the frontend and<br>
can watch most of the shows. But if I ESC the show, sometimes when I<br>go back to the same show, it locks up. Sometimes they don't lock up,<br>just show a black screen. Once one show won't play, nothing will and<br>
I either have to restart X or the reboot the computer.<br><br>I have a combined system mythbuntu 8.04 and a frontend only <a href="http://8.04.1./" target="_blank">8.04.1.</a><br>Both frontends experience the same problem, which to me points to the<br>
backend. I have had to restart the backend a couple time to get the<br>system going again.<br><br>I see lots of errors that just started in the backend log about the<br>same time this problem started. Older logs show no errors. The only<br>
thing I have done is get this frontend only system running but have<br>not touched the combined system at all.<br><br>The most interesting errors from mythbackend.log look like this:<br><br>2008-08-15 14:18:23.501 DB Error (Error in JobQueue::GetJobCmd()):<br>
Query was:<br>SELECT cmds FROM jobqueue WHERE id = 340;<br>Driver error was [2/2006]:<br>QMYSQL3: Unable to execute query<br>Database error was:<br>MySQL server has gone away</blockquote>
<div> </div>
<div>Looks like your database is crashing. Seems to be a MySQL problem. I would suggest updating your mysql-server packages unless you recently updated them prior to this issue then moving back to the previous version might be an option. Check you /var/log/mysqld logs to see what might be going on. If the database disappears, Myth will exhibit all sorts of problems.</div>
<div> </div>
<div>The script you're looking for is myth_optimize_db.pl I think. You can also just use the standard mysqlcheck program (which is what the script does) and refer to the MySQL documentation on diagnosis and recovery if you have bad tables.</div>
<div> </div>
<div>Kevin</div></div></div>