I tried the settings script and got the following output



the second output "HostMysqlserver localhost linhesserver"
may suggest that something is wrong but im not sure how to proceed since Ive never worked with databases.. I could probably look it up but Im afraid to break someting..
even the first output may indicate that I have to change that too?

/etc/hosts seem to be in order

The settings utility will also let you poke values into the settings table:

Most of the settings are stored in a very simple three column table, which lists the name, the value, and which machine it applies to. Values are looked up using the name and hostname (machine). A record with no hostname means that it is the global default and applies to all machines that don't have specific settings of their own. Given that, what the commands above are doing should be fairly obvious. If you run settings.sh -h it will print a command line usage summary.

thanx for the script. this will probably get handy several times in the future i guess.
Obviously my database had some errors that I now have corrected with this script but I see no difference in the behaviour.. even after a restart.
Ive tried to insert both "linhesserver" and "192.168.0.102" in the database but the frontend still cannot connect/login to the database.

After the lang selection screen, when prompted for IP, database name, user and pass I press "next" and "finish" i get the error message
"Cannot login"

Could it be a mythtv user/pass issue? it shouldnt since the frontend was able to connect before i started to change the settings from "localhost" to "192.168.0.102".. so i guess the message "cannot login" is just a generic message that the frontend wasnt able to connect/login?

I appreciate all your help and I hope you haven't run out of ideas just yet.. I have no idea what could still be wrong...

You did a standalone installation. Have you changed the backend to be Master_backend?

no i havent done anything like that. do i have to? i only have one backend.
as it is now the local frontend cannot connect to the backend. could that be because i havent it set as a master backend? how do i do that?

mysql also needs permissions set to allow the database to be accessed by non localhost. I'm on the road at the moment so someone else can point you to the right settings. If you set your machine to be master backend it should have done this automatically. but it can be done manually. Google can help you with the right command including how to check.

hint: this is a mysql command not a shell command.

It can be changed in the Service Menu/LinHES Configuration/System Type.
Edit: make sure to do a backup first

If you can't start the frontend, it's hard to access the LinHES menus. Enter into an xterm window. that will allow you to change the host type from standalone to masterbackend, opening up the database for outside access. (not sure what all else it does) You may need to first to enable changing the host type.

I think what christ is refering to in commenting out the 'skip-networking' in /etc/my.cnf and restart mysql to enable outside access. (line 39 in my config file)

Thanx everybody for helping me. IT was very much appreciated. I was starting to get frustrated -I finally solved it.
I probably didnt read the documentation well enough. As I understood it; "master backend" should only be chosen if more than one backend was to be used in the system. Now i know that "standalone" disables all non-localhost to access mysql.

I commented the "skip-networking" setting i my.cnf and Voilá!
the frontend was able to connect again.

thx

i was wondering..
now that the frontend connect to the backend im able to access the LinHES settings/system type
but the option where I choose "standalone/masterbackend etc." is greyed out and says "Standalone".

Would it be safer to do a reinstall selecting Masterbackend since it may otherwise cause other problems with my system later on? I mean, does the "master backend" setting change more stuff than the "skip-networking" in my.cnf?
My feeling is that by only commenting the "skip-networking" i may miss other settings that are done automatically when selecting master backend during installation...
any thoughts?

Right, but refer to very first line of this thread. That machine was accessible for change.

Sorry, I interpreted that as meaning the frontend would no longer run. Oh well, it works now.

goonzo: Service Menu>LinHES Configuration>Access Control
select 'Change hostype' and finish.
then go back to Service Menu>LinHES Configuration>System Type and you should be able to change from Standalone to Masterbackend.

I'm not sure what all else that will change besides the database, but I remember looking through an upgrade script one time and it took a different path depending on what system type was selected. Probably be a good idea to fix it now before you forget about it and it bites you on an upgrade later on.

Whoops, sorry goonzo, I thought you'd already taken care of that.

just to be safe i did a fresh install as "master backend" and it works. both my frontends can now connect

now begins the time consuming work of configuring everything!

again, thx for all support