I've just been upgrading my R5B7 to R5E50 and everything seems to have gone ok apart from the frontend not being able to contact the backend. The Frontend and backend are on the same machine.

In mythtv-setup I've setup both IP address to being 192.168.x.x.

I can see that the mythbackend is running using top, and looking in the logs for the mythbackend it appears to be up and working.

Both the Frontend and MythWeb are unable to see the backend server. Have I missed something obvious? I did perform a netstat -a and I couldnt see the ports open that I would expect 6543/6544.

Any help would be greatly appricated.

Looks like I've found my problem, because I'd setup the ip as 192.168.x.x, I have to update my /etc/hosts file so that mythtv was pointing at 192.168.x.x

Just in case anyone gets into the same problem as me. I hit a similar problem to this one where the mythbackend was running but never opened the ports 6543 and 6544.

Finally (with help) we got to the bottom of the problem, I'd added a new TV card and added it to to mythtv like normal. Unfortunately when the system had booted it found my new card before one of my old cards and so when the mythbackend start it was trying to use incorrect drives to access the cards. This causes the mythbackend to pause waiting for the card. But it never seems to return any error messages to the logs.

To fix the problem is was a simple fix of delete all my TV cards and redefine them, then the backend started correctly

Hi this is exactly my problem.
Mythbackend is waiting cause the id's of my videocards changed.

PVR 350 -> /dev/video0
BT878 -> /dev/video1

but in the setup it is display vice versa

PVR 350 -> /dev/video1
BT878 -> /dev/video0


My problem is that they change sometimes when I reboot my system.
Any ideas how I can prevent this?

Thanks for any suggestions.
Bube

Search for the posts by bruce_s01 on pinning down the udev definitions so that the cards get consistent names.

Wow this was a fast answer
I tried it and it seems to work.

Thx a lot!