On 05/08/2012 10:58 AM, Thomas Mashos wrote:
On Tue, May 8, 2012 at 10:34 AM, Eric Shubert<e...@shubes.net> wrote:
I recently upgraded my mythbuntu backend (.24) to the mythbuntu
repositories. When I did, my frontends could no longer connect to the
backend. The culprit was in /etc/mysql/mysql.cnf:
bind-address = 127.0.0.1
I changed this to the address of my network card, restarted mysqld, and
connections are now successful again.
Is this a bug that needs fixing, or is this set somewhere in the gui
configurations that I'm not seeing?
--
-Eric 'shubes'
--
Ubuntu-mythtv mailing list
Ubuntu-mythtv@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-mythtv
That should be set in /etc/mysql/mythtv.cnf
Thanks,
Thomas Mashos
I do have /etc/mysql/conf.d/mythtv.cnf which contains:
[mysqld]
bind-address=0.0.0.0
According to the mysql doc, 0.0.0.0 is the default value, and the server
should accept connections on all host IPv4 interfaces with this setting.
This setting apparently doesn't override the 127.0.0.1 value from the
my.cnf file. When I comment out
bind-address=127.0.0.1
in the /etc/mysql/my.cnf file, it works as it should (accepts
connections from the nic).
So the problem appears to be that the setting in mythtv.cnf (0.0.0.0)
does not override the setting in the my.cnf file. I guess that mysql
doesn't allow this setting to be reset to zeros once it's set to an
explicit address. :( ?
It looks as though the proper fix for this is to comment out (or remove)
the bind-address=127.0.0.1 parameter in the my.cnf file. I don't see any
purpose for it, especially in a backend host.
--
-Eric 'shubes'
--
Ubuntu-mythtv mailing list
Ubuntu-mythtv@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-mythtv
