[mythtvnz] New Backend / Existing Frontends

[Brett Miller]

 From my limited experience...
You need a static IP on the SQL database server box.
This IP can not be local loopback if you have multiple BE or FE on a 
network working as one system.
Only the local machine can see the SQL database if IP is local loopback.

Could achieve static IP via setup in your DHCP server (PC box or 
router/BB modem) by using MAC or name resolution tricks.
(can allocate same IP for the matching MAC address which is fixed to 
hardware or name)
Ubuntu Gnome 9.04 does seem to allow static IP config via GUI so need to...
Or remove the DHCP client from Ubuntu (dhcp-client3 )& edit the 
"/etc/network/interfaces"  file.
Config DHCP server (if you have) to exclude the IP numbers you want to 
allocate manually.
May need to add DNS settings into /etc/resolv.conf

There is a database procedure to complete when you want to change from 
127.0.0.1 local-loopback to a real IP....& before you run any backend 
processes.
This procedure stops your old records disappearing into the ether ??
This procedure is documented on MythTv site.

I changed BE IP addr, used above procedure (Mythtv database script) & 
did not lose any recordings only BE configuration.


On 11/02/2010 12:36 p.m., Tortise wrote:
> Replying to all posters, (thank you)
>
> I replaced the FE/BE box HDD with a new 1.5TB, so only thing new is the HDD and software.  Rest is known working hardware.
>
> Running MCC from a FE shows the mySQL connection is failing to connect.
>
> Running
> sudo dpkg-reconfigure mythtv-database
> sudo dpkg-reconfigure mythtv-common   (Replaced localhost with FE/BE IP)did not help.I'd earlier overwritten localhost in the
> General setup and that IP remained correct.running this gives:~$ sudo iptables -L[sudo] password for user:Chain INPUT (policy
> ACCEPT)target     prot opt source               destinationChain FORWARD (policy ACCEPT)target     prot opt source
> destinationChain OUTPUT (policy ACCEPT)target     prot opt source               destinationI presume this means its running in a
> default config, I've never changed the mythbuntu settings for this and there is remote access to the machine, e.g. mythweb ssh and
> VNC.
>
> I've decided to just run the install up again as I think what I might have done worng was not check the allow other users to connect
> box when it asked me during the faulty install and it seems hard to fix that now.  I think the fix might lie in the MySQL however
> that's not a good place for me to muck around.
>
> I do find the users a little confusing, as it seems, by default, there are two users, "mythtv" and your nominated logon say
> "mylogon".   Remote FE seem to want to connect as mythtv however it seems one run the FE/BE as "mylogon"  It seems using
> tv_grab_nz-py that one needs to configure both /home/mythtv/.mythtv and also /home/mylogon/.mythtv to get universal access.   Can
> anyone clarify this further?  Would using "mythtv" as the logon be better?  Perhaps there are good reasons not to do this?
>
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz at lists.linuxnut.co.nz
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.435 / Virus Database: 271.1.1/2678 - Release Date: 02/09/10 19:35:00
>
>    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ourshack.com/pipermail/mythtvnz/attachments/20100212/e93aee53/attachment.htm