[mythtv-users] 0.28 upgrade issue frontend connection

Mark Perkins perkins1724 at hotmail.com
Mon Jul 18 03:37:10 UTC 2016


> 
> Neither option caused mythweb to work.
> 
> With db server at 127.0.0.1:
> 
> $ sudo netstat -peanut | grep 6543
> [sudo] password for dpeale:
> tcp        0      0 127.0.0.1:6543          0.0.0.0:*               LISTEN      124        22761
> 1433/mythbackend
> tcp6       0      0 ::1:6543                :::*                    LISTEN      124        22762
> 1433/mythbackend
> 
> with dbserver at 192.168.63.3:
> 
> $ sudo netstat -peanut | grep 6543
> [sudo] password for dpeale:
> tcp        0      0 127.0.0.1:6543          0.0.0.0:*               LISTEN      124        23751
> 1414/mythbackend
> tcp6       0      0 ::1:6543                :::*                    LISTEN      124        23752
> 1414/mythbackend
> 

Interesting. Your backend is not listening on the 192.168.63.3 IP address. I wonder if there is some other network issue at play. The startup section of the mythbackend log file might reveal more.

Did the error message in mythweb change to follow the 127.0.0.1 address when  setenv db_server  "127.0.0.1", and 192.168.63.3 when setenv db_server "192.168.63.3"?

In mythtv-setup / general what values do you have set for Local Backend IPv4 address and Master Backend IPv4 address?

I'm rapidly running out of ideas. At this point I would try setting both Local Backend IPv4 address and Master Backend IPv4 address to 127.0.0.1 in mythtv-setup / general. I would set setenv db_server  "127.0.0.1" in mythweb.conf and confirm that the error message given when trying to access the webpage changes to point to 127.0.0.1 not 192.168.63.3. I would also change config.xml to point to 127.0.0.1.

Did you restart apache2 after updating the conf file each time? 
What does ifconfig show?


More information about the mythtv-users mailing list