LinHES Forums
http://forum.linhes.org/

Backend crashes when loading Recorded Program page MythWeb
http://forum.linhes.org/viewtopic.php?f=6&t=13791		 Page 1 of 1
Author:  jmhunt [ Tue Jan 23, 2007 9:31 pm ]
Post subject:  Backend crashes when loading Recorded Program page MythWeb
Anyone have an idea why my MythBackend crashes when I via the Recorded Programs through MythWeb.

I click on the link that brings up the list of Recorded Programs and the backend almost always crashes. I get the following error in my browser:
Code:
Error at /usr/share/mythtv/mythweb/includes/mythbackend.php, line 105:
fsockopen(): unable to connect to 127.0.0.1:6543
Details:

    datetime:  2007-01-21 18:13:32 (EST)
    errornum:  2
  error type:  Warning
error string:  fsockopen(): unable to connect to 127.0.0.1:6543
    filename:  /usr/share/mythtv/mythweb/includes/mythbackend.php
  error line:  105

Error at /usr/share/mythtv/mythweb/includes/mythbackend.php, line 105:
fsockopen(): unable to connect to 127.0.0.1:6543
Details:

    datetime:  2007-01-21 18:13:33 (EST)
    errornum:  2
  error type:  Warning
error string:  fsockopen(): unable to connect to 127.0.0.1:6543
    filename:  /usr/share/mythtv/mythweb/includes/mythbackend.php
  error line:  105




System is a combined frontend/backend with 2 pcHDTV HD3000 and using the FireWire connection to the DCT-6200 cable box. I'm using R5D1. Except for the occasional crashes when fast forwarding, the box is pretty stable.
Author:  jmhunt [ Tue Jan 23, 2007 9:34 pm ]
Post subject: 
In case it helps, the error in my /var/log/mythtv/mythbackend.log is:
Code:
[mpeg2video @ 0xb7082620]get_buffer() failed (stride changed)
2007-01-23 22:30:28.463 AFD Error: Unknown decoding error
[mpeg2video @ 0xb7082620]get_buffer() failed (stride changed)
2007-01-23 22:30:28.467 AFD Error: Unknown decoding error
2007-01-23 22:30:34.447 Event socket closed. No connection to the backend.


Also, in case it is related. When this problem occurs, the free space at the end of the Recorded Program's page is messed up.

For example
Quote:
136 programs, using 153 GB (94 hrs 8 mins) out of B ( B free).
Author:  arriflex [ Sun Oct 07, 2007 5:50 pm ]
Post subject: 
Did you ever figure this one out? I've just started having a extremely similar problem.
arri
Author:  Too Many Secrets [ Sun Oct 07, 2007 7:12 pm ]
Post subject: 
I've seen this a couple times, it was always related to database errors resolved following the instructions here.
Author:  tjc [ Sun Oct 07, 2007 8:13 pm ]
Post subject: 
The script here is also good for db repair as well as optimization. http://mysettopbox.tv/phpBB2/viewtopic.php?t=15694 It automates all the steps needed and falls back on a slower but safer technique when necessary.
Author:  Too Many Secrets [ Sun Oct 07, 2007 9:28 pm ]
Post subject: 
tjc wrote:
The script here is also good for db repair as well as optimization. http://mysettopbox.tv/phpBB2/viewtopic.php?t=15694 It automates all the steps needed and falls back on a slower but safer technique when necessary.


Nice, I've copied the above script and will use it next time I have a problem. How is the above different from the optimize_mythdb.pl included script?
Author:  arriflex [ Mon Oct 08, 2007 9:35 pm ]
Post subject: 
Great, thanks. tjc's script definitely did the trick in more ways than one. The whole box seems snappier. (could just be wishful thinking)

For the noob that I am, I used chmod +x to get it to run after writing the script in /usr/local/bin. Was this proper or how should I have handled it?

arri
Author:  marc.aronson [ Mon Oct 08, 2007 10:24 pm ]
Post subject: 
arriflex wrote:
The whole box seems snappier. (could just be wishful thinking)
arri


It's not your imagination -- you will see better performance anytime you are doing database intensive activities such as getting a list of recorded shows, looking at the TV listings, etc.

Marc
Author:  tjc [ Mon Oct 08, 2007 11:13 pm ]
Post subject: 
arriflex wrote:
For the noob that I am, I used chmod +x to get it to run after writing the script in /usr/local/bin. Was this proper or how should I have handled it?

Absolutely correct.
Author:  tjc [ Mon Oct 08, 2007 11:17 pm ]
Post subject: 
Too Many Secrets wrote:
How is the above different from the optimize_mythdb.pl included script?

The Perl script uses SQL commands via the mysql daemon. The shell script bypasses the daemon and gets down and dirty directly with the ISAM files. It also avoids probing for the mysql.txt file which could find extraneous files which are not normally used. The hope was that these would make it more robust.
Author:  Too Many Secrets [ Mon Oct 15, 2007 10:42 am ]
Post subject: 
Too Many Secrets wrote:
I've seen this a couple times, it was always related to database errors resolved following the instructions here.


OMG, I spoke too soon... So away from home for a week, check to make sure I recorded what I wanted and BAM! backend dies, gives me the /ipaddress/:xxxx is backend running? Of course it wasn't. Run the above script and test, BAM! again. MythWeb is fine as long as I don't view the Recording page.

So I don't currently see any database errors, but backend crashes when access MythWeb Recordings. I will have to wait a while to diagnose.
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/