[mythtv-users] COnfused: Backend IP change kills recording

[Nick Rout]

On Tue, Jul 1, 2008 at 9:03 AM, The GUIGuy <linux at finalfiler.com> wrote:
> When I ran my Mythbuntu install, it set the MythTv and the MasterServer
> IP addresses 127.0.0.1
>
> This is, as I understand, OK for a single front/ backend combination.
>
> Now I wanted to run a second remote frontend. According to the MythTV wiki
>
> http://mythtv.org/wiki/index.php/User_Manual:Detailed_configuration_Backend
>
> [QUOTE]
> IP address for mythtv
>
> Enter the IP address of this (backend) machine. Use an externally
> accessible address if you are going to be running a frontend or Slave
> Backend on a different machine than this one. (ie, not 127.0.0.1)
> MythTV is made up of two major components, the Backend and the Frontend.
> If you run the Backend and Frontend on the same machine then you can
> leave the setting at its default value of 127.0.0.1. This is referred to
> as the local loopback address which is reserved for networking within a
> single machine. If you run multiple frontends, or run frontends over
> network connections on different machines, then you will need to set
> this to the backend machines' static IP address. This value will be
> determined by your TCP/IP Network addressing scheme.
> [/QUOTE]
>
> For the Master IP address it says
> [QUOTE]
> The IP address of the master backend server. All frontend and non-master
> backend machines will connect to this server. If you only have one
> backend, this should be the same IP address as above. [/QUOTE]
>
>
> Here's my problem; if I change the IP address to the backend PCs IP
> address, 192.168.1.6 I can access the backend OK remotely.
>
> However, I cannot record or set recording schedules. In fact, all the
> existing recording schedules disappear!!
>
> If I put the IP addresses on the backend back to 127.0.0.1 (localhost)
> my recording schedules are back and I can record again.
>
> Not being the sharpest tool in the shed I am totally confused about this
> behaviour.
>
> Any help?

Possibly to do with whether mysql is authorised to allow access by
your backend process from 192.168.1.6 (as opposed to 127.0.0.1)