MythTV 0.25

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Upgrade to 0.25
2.
3.

What is the expected output? What do you see instead?
A working connection.
Connection refused.

What version of the product are you using? On what operating system?
1.7.1, Android 2.3.X

Please provide any additional information below.

Original issue reported on code.google.com by kiwin...@gmail.com on 24 Apr 2012 at 9:44

[GoogleCodeExporter]

I ran into this issue as well.  I believe it is a bug with mythtv 0.25 where 
mythfrontend's telnet interface does not listen on the correct IP address.  I 
opened a ticket with MythTV: http://code.mythtv.org/trac/ticket/10654

If you are running the frontend and backend on the same machine, you can 
workaround the issue by setting your backend server to listen on your LAN 
address instead of 127.0.0.1

Original comment by jrsan...@gmail.com on 25 Apr 2012 at 5:44

[GoogleCodeExporter]

Thanks. Will keep an eye on there too :)

Original comment by kiwin...@gmail.com on 25 Apr 2012 at 6:49

[GoogleCodeExporter]

I, too, am having the same problem.  MythMote used to work on .24.  I am now 
getting "IO Except ... Connection Refused" on 0.25.  Android App MythFrontEnd 
connects fine.  Per above, I changed all occurrances from localhost, loopback, 
or 127.0.0.1 to the IP address of the (unified) frontend / backend.  Android 
Version 2.2.2

Original comment by rays...@gmail.com on 15 May 2012 at 9:05

[GoogleCodeExporter]

Have you changed it in mythbackend?

Original comment by kiwin...@gmail.com on 15 May 2012 at 9:09

[GoogleCodeExporter]

I had to re-enable network remote control in the frontend when I upgraded to 
mythtv 0.25. It usually requires restarting the frontend application too. My 
0.25 frontend would also ask for the CD/DVD device upon start and at that point 
the network remote interface was not started and I had to walk ( how horrible ) 
over to the machine and use the keyboard. Once it made it to the main menu the 
interface would be up and mythmote worked. If anyone has any other debug 
information let me know and I can take a look.

On a side note Mythtv 0.25 brings a new services API which will allow mythmote 
to communicate with frontends via a REST API. I'm currently working on Dan 
Frey's mythtv-for-android to integrate mythmote functionality using the 
services API. Once mythtv-for-android is out in beta I'll create mythmote2 from 
the work done on mythtv-for-android. Dan implemented some nice auto discovery 
of backends and frontends that will help with issues like this and I plan on 
using it in mythmote2. The plan is Mythmote2 uses Services API and supports 
Mythtv 0.25+. Mythmote1 will be maintained for previous versions of Mythtv.

If your interested in Dan's project its over at github: 
https://github.com/dmfrey/mythtv-for-android

-Tom

Original comment by tom...@gmail.com on 22 May 2012 at 3:08

[GoogleCodeExporter]

Is there any solution for a separate myth-frontend 0.25 and the existing 
mythmote? Or do we need to wait for mythmote2/mythtv-for-android?

Original comment by e...@mcdonagh.org.uk on 11 Jun 2012 at 8:07

[GoogleCodeExporter]

Hi ed, what are you looking for a solution to?

Original comment by tom...@gmail.com on 14 Jun 2012 at 11:51

[GoogleCodeExporter]

I had an ubuntu 11.10/mythtv 0.24 front/back-end upstairs, and an ubuntu 
11.10/mythtv 0.24 downstairs. Mythmote worked very well, and helped massively 
with the girlfriend (or in my case wife) test!

I then upgraded to ubuntu 12.04 on both computers, and therefore to mythtv 
0.25. Mythmote no longer works, as many people have found - IO Except: failed 
to connect to...

Most workarounds seem to assume that you are communicating with a sole 
front/back-end, and they don't seem to make sense for a stand alone front end. 
This is what I need a solution to.

You however don't seem to have had this problem yourself, which doesn't make 
sense to me! My understanding was that with 0.25 the network remote control 
only listens on the loopback address.

Any ideas for a solution? If I can supply any debug from phone or PC, please 
point me in the right direction.

Thanks

Original comment by e...@mcdonagh.org.uk on 14 Jun 2012 at 7:26

[GoogleCodeExporter]

As per Ed above - I am having the same issue now that I have a new MythFrontend.

Ed - if you look at the Trac ticket for MythTV they have dismissed this as 
'just how the system works now we have the new connection stuff' - meaning we 
have to wait for mythmote2/mythtv-for-android :(

Original comment by kiwin...@gmail.com on 14 Jun 2012 at 8:06

[GoogleCodeExporter]

Also: https://github.com/MythTV-Android/mythtv-for-android/downloads is the 
correct URL :)

Original comment by kiwin...@gmail.com on 14 Jun 2012 at 8:40

[GoogleCodeExporter]

Once mythtv-for-android is in beta I'll pull what I need from it to make 
mythmote2 and post that here.

I did a fresh install of mythbuntu and upgrades and all worked fine. The only 
issues I've had were firewalls and having to turn the network remote interface 
back on in the frontend general settings. There has to be something different 
about your installations because I know others that have upgraded and mythmote 
still works.

Did you try nmap [frontend ip] ? I'd try this from the frontend machine itself 
and from another machine.

IPv4 or IPv6 network? I only use IPv4 for my home network.

-Tom

Original comment by tom...@gmail.com on 16 Jun 2012 at 1:49

[GoogleCodeExporter]

Hi Ed.
I found I could get my remote working again by disabling it in the general 
settings, restarting the front end. Then enabling it again and restarting the 
front end again.

- Scott

Original comment by klu...@gmail.com on 19 Jul 2012 at 10:01

[GoogleCodeExporter]

Following a hint I found about this issue on askubuntu, I was able to work 
around this problem using ConnectBot and doing a little port forwarding. 
Basically you ssh into the mythfrontend and forward port 6456 to the android 
device. This allowed mythmote to connect to the loopback address on the android 
device and work normally. Thanks for this great app!

http://askubuntu.com/questions/127445/mythmote-wont-connect-to-mythbuntu-12-04-s
eems-frontend-is-not-listening-on-all

Original comment by richardm...@gmail.com on 25 Jul 2012 at 12:35

[GoogleCodeExporter]

Original comment by tom...@gmail.com on 17 Oct 2012 at 2:25

• Changed state: Done

[GoogleCodeExporter]

As a follow-up, the 
http://askubuntu.com/questions/127445/mythmote-wont-connect-to-mythbuntu-12-04-s
eems-frontend-is-not-listening-on-all link now shows a much simpler solution 
which worked for me on my combined front/backend mythbuntu setup.

- Run sudo mythtv-setup as the user that normally runs the frontend.

- Enter General Configurations, and change the IP address to match the 
external, network IP address. In my case I set the ipv4 address, and left ipv6 
blank.

Original comment by ctd....@gmail.com on 10 Dec 2012 at 12:44

[GoogleCodeExporter]

I wasted much time on this. Easier and more universal way is to redirect the 
port on the frontend machine rather each android or other device by using 
xinetd on the frontend (using Ubuntu below):

 - Install the super-server using "sudo apt-get install xinetd"
 - as root add a new config file in "/etc/xinet.d/" with the following contents:

service mythremote
{
    disable                 = no
    type                    = unlisted
    socket_type             = stream
    wait                    = no
    user                    = nobody
    redirect                = 127.0.0.1 6546
    bind                    = ###put your frontend machine IP address here##
    port                    = 6546
}

 - Restart xinetd using "sudo service xinetd restart" to pick up the new config.

Now a "sudo netstat -lnp | grep 6546" on the frontend should show mythfrontend 
listening on port 6546 on the loopback and xinetd listening on the external 
address that was edited into the file. Static IP is obviously necessary for 
this also.

This worked perfectly on my 0.26 standalone frontend machine.

Original comment by markkbo...@gmail.com on 2 Feb 2013 at 9:18

[GoogleCodeExporter]

I had xinetd working with mythtv 27 version and mythmote. Then I installed the 
upgrades which fixed the hdmi loss of signal and video stutter after playing 
around with video options. So if you are using mythtv 27.3 and ubuntu trusty 
(14.x.x). Install xinet.d and I posted updated config file that you put into 
/etc/xinet.d/. I just got it to work after researching xinetd options. Again 
this works for the users who have a single machine running both mythtv front 
and backends on the Ubuntu 14.x.x LTS. 

Original comment by SCab...@gmail.com on 13 Oct 2014 at 3:21

[GoogleCodeExporter]

Ok here is the promised configuration file that you modify and put in the 
"/etc/xinet.d/" directory. I put comments explaining the ones that I researched 
to do what I wanted for allowing mythmote to work for my machine. The only 
thing I noticed is the first time you boot up your computer is that you have to 
allow it more time to the the main menu at least on my machine which is not the 
fastest machine on the block. So you mileage may vary.

Original comment by SCab...@gmail.com on 23 Oct 2014 at 12:09

Attachments:

• mythremote.conf