On Sat, August 11, 2007 6:06 pm, Urivan Saaib wrote: > Lan, > > If you update mysql.user to host='%' where user='mythtv', and then > 'flush > privileges', can you still connect? > > Is the client using localhost as the destination host of the mysql? If so, > that's the reason why it fails when you change it to 192.168.1.0.
Urivan, As best I can tell, the 192.168.1.0/255.255.255.0 semantics is a mysql thing (from the documentation on mysql.org) meaning "requesting IP & mask == this IP". It is yet another expression of 192.168.100.%. One of my gripes about mysql so far is that I have seen so many ways of expressing this wildcardness, and a lot of them haven't worked. Some people report that they have no joy until they enter a rule explicitly for each remote FE's IP. Besides, I'm really confused as to why one FE can connect but neither the BE (as client to itself) or another FE can. It seems to me that is one FE can connect, the problem is not in mysqld. The problem must be in some kind of FE config. But that assumption may be wrong. I'm chasing down other stuff from here and the Mythtv list. Alas it's not as much fun as it should be. I'm getting a lot of spousal dissaproval because, while she likes having the recorder just fine (and the kids would rise up in revolt if it went away), when I have to give it some of my time that she thinks belongs to her, she gets resentful. > > Regards, > > -Urivan Flores-Saaib > > > ==============Original message text=============== > On Sat, 11 Aug 2007 17:26:26 PDT "Lan Barnes" wrote: > > I have diagnosed this and am convinced it is strictly a mysql > configuration problem. > > I have a mythtv BE/FE one one box in working order. I want to put remote > FEs on other machines. I had this working before but reinstalled my myth > box. Of course I've forgotten how. > > I have granted all on mythconverg.* to mythtv at > "192.168.1.0/255.255.255.0". I have selected from the mysql.user table and > those privileges are in there. > > I change my database ip in mythsetup from localhost to either the ip addr > or the BE's name. myth loses its connection when I do this and gets OK > when I change it back to localhost. > > But here's the interesting thing. Consider the results when I try > connecting with mysql from three machines: > > Connection command line was the same from each test host: > > mysql -h xena -u mythtv -p mythconverg > > 1. From the myth FE/BE (xena) newly upgraded: failure to connect to > 'localhost' > > 2. from my laptop (gypsy) never configured to be a remote FE: failure to > connect to 'gypsy' > > 3. from a workstation previously successfully configured to be a remote FE > to the old mythtv installation: success! > > I've compared the /etc/my.cnf from the successful machine and the others. > No difference. Also, nothing special in the environment variables on the > working machine. > > So I'm thinking, there is some configuration on the client machine that > makes this connection possible over tcp/ip, even if the client is on the > same machine as the backend. > > OR something broke in mysql between mythdora 3.2 and 4.0, which is > unlikely because the mythdora mailing list would be awash in complaints, > which it isn't. > > Does anyone know what I need to do to make the FE/BE mysql see itself over > tcp/ip? > > -- > Lan Barnes > > SCM Analyst Linux Guy > Tcl/Tk Enthusiast Biodiesel Brewer > > > > > > > -- > KPLUG-List@kernel-panic.org > http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list > ===========End of original message text=========== > > > > -- > KPLUG-List@kernel-panic.org > http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list > -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- KPLUG-List@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
