View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 11 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Tue Jan 23, 2007 9:31 pm 
Offline
Joined: Sun Jul 18, 2004 6:24 pm
Posts: 84
Location: Medford, Massachusetts
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.

_________________
AMD Athlon 64 3000+ on MSI K8T Neo
FX5200
pcHD3000
Firewire to Comcast cable box
PVR-250
R6


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jan 23, 2007 9:34 pm 
Offline
Joined: Sun Jul 18, 2004 6:24 pm
Posts: 84
Location: Medford, Massachusetts
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).

_________________
AMD Athlon 64 3000+ on MSI K8T Neo
FX5200
pcHD3000
Firewire to Comcast cable box
PVR-250
R6


Top
 Profile  
 
 Post subject:
PostPosted: Sun Oct 07, 2007 5:50 pm 
Offline
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
Did you ever figure this one out? I've just started having a extremely similar problem.
arri

_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27


Top
 Profile  
 
 Post subject:
PostPosted: Sun Oct 07, 2007 7:12 pm 
Offline
Joined: Fri Oct 20, 2006 12:04 pm
Posts: 905
Location: LA, CA
I've seen this a couple times, it was always related to database errors resolved following the instructions here.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Oct 07, 2007 8:13 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
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.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Oct 07, 2007 9:28 pm 
Offline
Joined: Fri Oct 20, 2006 12:04 pm
Posts: 905
Location: LA, CA
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?


Top
 Profile  
 
 Post subject:
PostPosted: Mon Oct 08, 2007 9:35 pm 
Offline
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
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

_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27


Top
 Profile  
 
 Post subject:
PostPosted: Mon Oct 08, 2007 10:24 pm 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1532
Location: California
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


Top
 Profile  
 
 Post subject:
PostPosted: Mon Oct 08, 2007 11:13 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
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.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Oct 08, 2007 11:17 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
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.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Oct 15, 2007 10:42 am 
Offline
Joined: Fri Oct 20, 2006 12:04 pm
Posts: 905
Location: LA, CA
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.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 11 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 14 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu