Hey all,

My mythweb was working perfectly yesterday but I had to pick it up and move it to my friend's place and now my MythWeb is running into these errors:

Warning at /usr/share/mythtv/mythweb/includes/mythbackend.php, line 102:
fsockopen(): unable to connect to 127.0.0.1:6543 Fatal Error at /usr/share/mythtv/mythweb/includes/mythbackend.php, line 32:
Unable to connect to mythbackend, is it running?

The system administrator has been notified and the problem will be remedied shortly.

The apache server is working because I can connect to the box. It's not until I click MythWeb that I run into these errors.

Since I am the system administrator, could anyone explain to me how I might remedy the problem?

Thanks so much.

You need to check that mythbackend is running as the error message states. There is a couple of ways to test this:

1. If you knoppmyth box is setup to watch tv, if you select this option and you can watch tv, the problem is somewhere else. If it doesn't work you will get an error message saying a similar things in that it can't connect to the backend.

2. ssh into your and run and this print the details of the mythbackend process if it is running. If not your should see nothing come back except the command prompt.

If you don't find it running, the easiest and safest thing to do is reboot your box. You could also run it from a command line and it will display messages about what it is doing.

If you find it won't run, do a search of the forum because I know that this topic has been discussed before.

Cheers,
Girkers

_________________
Girkers

I'm plugging it into my monitor to test right now but I SSHed in and got this:

4016 ttyp0 S+ 0:00 grep mythbackend


from the command you listed here. So, I think it's running? Rebooting the thing now and we'll see.

I went to watch TV and it said it couldn't contact the myth backend server. You were absolutely right. I'll start looking through the forums for answers now.

Someone said that I needed to set my IP Address from 127.0.0.1 to localhost but this didn't fix the problem. Anyone have any idea as to what is going on and what I may have changed?

EDIT: Upon further inspection, I believe the problem may revolve around the fact that the machine can ping 127.0.0.1 but not 127.0.01 6543 (the mythtv port.) Can anyone suggest a way of fixing this?

After scanning the forums for a while I think I found my unique problem:

When I try to start the backend as root I get this error:
root@chronos:~# /etc/init.d/mythtv-backend start
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

sit0: unknown hardware address type 776
wlan0: ERROR while getting interface flags: No such device
sit0: unknown hardware address type 776
Bind socket to interface: No such device
exiting.
root@chronos:~#


I'd been fooling with getting my Wireless USB Device working which involved an update to the rc.d? file and I think it's pulling it's networking settings from there. I -did- manage to get wireless working. However, now I want to revert to using eth0. Can anyone help me correct this error?

You may want to ssh in again and run this command:


This will allow you to configure your network card. Prior to this you may wish to try as this will give you the details of your configured network cards.

_________________
Girkers

this, to me looks like the backend IS NOT RUNNING.

the output of the ps command should locate two processes, one should be the backend and the second sould be the be the 'grep mythbackend' process. Your output only includes the grep. Hrer is mine:



Check your logs for backend issues (/var/log/mythtv/mythbackend.log). you can start the backend in an xterm and watch the output on the screen as well.

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

I got up this morning and ran the commands you all suggested.

grep | mythbackend seems to start the backend process but it hangs indefinately at




maybe it's supposed to?

I'm connecting to the internet fine because I can SSH into the machine and reach google and other websites without any trouble.

Net card config said --



I still think it might have something to do with that update-rc.d command I ran to get my wireless card working. I had to post in another forum to get that help I needed to get it to work but my .sh file included the commands



Here's the PS Command:



Thanks for the initial responses. I'll keep grabbing any information needed.
[/code]

It's funny how some things happen. I got this exact error this evening and found that it was because my backend was not running.

Now you can start the backend in one of two ways.

1. To run it and see what is going on, SSH into your knoppmyth box and run
You will then be able to see what is going on.

2. To run it as it is supposed to be


[edit]typo

_________________
Girkers

not like this

there is a big diffence. The first command line say "search and send the output of the search to the input of mythbackend" But you are not telling grep (the search program) what to search for or where to look... so it hangs

The second line says "create a list of all process and send that list to the input of grep (the search program) and search for lines that contain the string 'mythbackend' You will hopefully see the process running mythbackend as well as the process executing the 'grep mythbackend' step

you may want to read teh man page for grep, it is a very useful tool

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

Alternatively:

intresting tlc,

well, I've grown up with aix, hp-ux and solaris. each of the commercial OS's have ps and grep. used to be more of a modular, pipeline approach. once you knew grep you could use it everywhere.

Seems the linux community takes the approach that it is good to replace with a sepatare binary with its own syntax to learn....smacks of academia. (i.e. little billy wrote a C program that combines grep and ps in his programming 101 class)

guess its OK, until you move to a different OS that doesnt include pgrep.

this was just an editorial from a 38 year old with aix, hp-ux, solaris. mvs, cics, cobol, vms, acms. No linux developers were injured in the production of this post.

anyone miss VAX DCL? ..f$string...global logicals?... RDB....DECForms?

Wow, this got off topic, sorry

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

Dude, I'm older than that.

I use pgrep where available because it's options are more consistent and easier for my poor old brain to remember... Now lets see, which ps style does this system prefer? "ps -elf"? "ps -auxw"? "ps auxw"? Oh nuts, what's the order of the columns with this flavor on this system again? ...

I am having a similar problem as the original poster- the backend not starting and then seeing the errors when attempting to do anything in the frontend. I tried Girkers suggestion and got some "odd" results.

When I do

I receive the following message:


If I run then the backend does indeed start and I must then run .

My network is working fine on boot, so I know that is not an issue. I don't know how/where to edit something so that the backend is started correctly upon boot.

Thanks in advance for any help you can offer!

- Katie